Skip to content

[3.11] gh-99659: Use correct exceptions in sqlite3 bigmem tests (GH-99660) #99666

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

Merged
merged 1 commit into from
Nov 22, 2022

Conversation

miss-islington
Copy link
Contributor

@miss-islington miss-islington commented Nov 21, 2022

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 [email protected]

…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 <[email protected]>
@miss-islington miss-islington merged commit e26aa24 into python:3.11 Nov 22, 2022
@miss-islington miss-islington deleted the backport-2781ec9-3.11 branch November 22, 2022 08:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tests Tests in the Lib/test dir
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants