Message393945
| Author | erlendaasland |
|---|---|
| Recipients | berker.peksag, erlendaasland, lemburg, serhiy.storchaka |
| Date | 2021-05-19.10:42:54 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1621420974.78.0.765808122112.issue44092@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
I've crafted a number of rollback tests, but it occurred to me that they are simply just testing SQLite behaviour; not sqlite3 behaviour. I had to adjust the tests according to which version of SQLite was used (for example 3.8.7.2 introduced new behaviour). Such tests are bound to break as SQLite evolves. I'm not sure we want such tests in our test suite; it can make the CI fail for completely unrelated PRs. Suggesting to leave detailed rollback testing to SQLite and just keep a couple of basic tests in our suite. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2021-05-19 10:42:54 | erlendaasland | set | recipients: + erlendaasland, lemburg, berker.peksag, serhiy.storchaka |
| 2021-05-19 10:42:54 | erlendaasland | set | messageid: <1621420974.78.0.765808122112.issue44092@roundup.psfhosted.org> |
| 2021-05-19 10:42:54 | erlendaasland | link | issue44092 messages |
| 2021-05-19 10:42:54 | erlendaasland | create | |