Skip to content
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

Merged
merged 1 commit into from
Nov 21, 2022

Conversation

ambv
Copy link
Contributor

@ambv ambv 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.

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.
@ambv ambv force-pushed the sqlite3-bigmem-dataerror branch from 3eec87c to 6d69bd1 Compare November 21, 2022 18:21
@ambv ambv added needs backport to 3.10 only security fixes needs backport to 3.11 only security fixes labels Nov 21, 2022
@ambv ambv merged commit 2781ec9 into python:main Nov 21, 2022
@miss-islington
Copy link
Contributor

Thanks @ambv for the PR 🌮🎉.. I'm working now to backport this PR to: 3.10, 3.11.
🐍🍒⛏🤖

@ambv ambv deleted the sqlite3-bigmem-dataerror branch November 21, 2022 20:44
@miss-islington
Copy link
Contributor

Sorry, @ambv, I could not cleanly backport this to 3.10 due to a conflict.
Please backport using cherry_picker on command line.
cherry_picker 2781ec9b0e41a62cecc189c22dfc849f9a56927c 3.10

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Nov 21, 2022
…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>
@bedevere-bot
Copy link

GH-99666 is a backport of this pull request to the 3.11 branch.

@bedevere-bot bedevere-bot removed the needs backport to 3.11 only security fixes label Nov 21, 2022
@ambv ambv removed the needs backport to 3.10 only security fixes label Nov 21, 2022
@ambv
Copy link
Contributor Author

ambv commented Nov 21, 2022

Nevermind the 3.10 backport, those test methods don't exist there (and the test file lives in Lib/sqlite/test/ on that branch).

miss-islington added a commit that referenced this pull request Nov 22, 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 <lukasz@langa.pl>
@ambv ambv restored the sqlite3-bigmem-dataerror branch December 5, 2022 16:30
@ambv ambv deleted the sqlite3-bigmem-dataerror branch November 1, 2023 13:15
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