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
bpo-45243: Use connection limits to simplify sqlite3 tests
#29356
bpo-45243: Use connection limits to simplify sqlite3 tests
#29356
Conversation
13a40b0
to
07d012a
Compare
07d012a
to
8cdb980
Compare
sqlite3 tests
|
If you want to schedule another build, you need to add the " |
Bigmem tests rewriting does not look correct to me. These tests are specially purposed to test the integer overflow. They try with scripts of specific length (slightly below or above INT_MAX). It does not make sense to test scripts with smaller length. They are decorated with bigmemtest because they require a large amount of RAM and should be skipped if it is not enough.
The C code explicitly checks the current connection limit (
cpython/Modules/_sqlite/cursor.c Lines 730 to 737 in 77a1f8d
cpython/Modules/_sqlite/statement.c Lines 62 to 68 in 77a1f8d
|
|
@serhiy-storchaka, let me know if you want me to revert the bigmem tests. I believe it is correct to change them, though (see my previous comment). |
|
Thanks for reviewing, @serhiy-storchaka. What do you think of my proposed patch in #29356 (comment)? I guess it is out of scope for this PR, but I think we should apply it. |
|
FYI, I'll merge in |
|
CI is ok; ready for merge :) I'll create an issue regarding the length checks. |
Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
build-in round is missing if SQLITE_OMIT_FLOATING_POINT is defined
|
Thank you for reviewing, Serhiy. The PR is in a better shape now. |
https://bugs.python.org/issue45243