-
-
Notifications
You must be signed in to change notification settings - Fork 31.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gh-99659: Use correct exceptions in sqlite3 bigmem tests #99660
Conversation
The tests in question were added in 0eec627 by Serhiy. Apparently, sqlite3 changed exceptions raised in those cases in the mean time but the tests never ran because they require a high `-M` setting in the test runner.
3eec87c
to
6d69bd1
Compare
Thanks @ambv for the PR 🌮🎉.. I'm working now to backport this PR to: 3.10, 3.11. |
Sorry, @ambv, I could not cleanly backport this to |
…nGH-99660) The tests in question were added in 0eec627 by Serhiy. Apparently, sqlite3 changed exceptions raised in those cases in the mean time but the tests never ran because they require a high `-M` setting in the test runner. (cherry picked from commit 2781ec9) Co-authored-by: Łukasz Langa <lukasz@langa.pl>
GH-99666 is a backport of this pull request to the 3.11 branch. |
Nevermind the 3.10 backport, those test methods don't exist there (and the test file lives in |
The tests in question were added in 0eec627 by Serhiy. Apparently, sqlite3 changed exceptions raised in those cases in the mean time but the tests never ran because they require a high `-M` setting in the test runner. (cherry picked from commit 2781ec9) Co-authored-by: Łukasz Langa <lukasz@langa.pl>
The tests in question were added in 0eec627 by Serhiy. Apparently, sqlite3 changed exceptions raised in those cases in the mean time but the tests never ran because they require a high
-M
setting in the test runner.