Bug report
In a755124 (GH-26728, v3.11.0a7), @erlend-aasland added a test_deserialize_too_much_data_64bit, which would instantly raise a NameError for size if run:
| @unittest.skipUnless(sys.maxsize>2**32, 'requires 64bit platform') |
| @bigmemtest(size=2**63, memuse=3, dry_run=False) |
| deftest_deserialize_too_much_data_64bit(self): |
| withmemory_database() ascx: |
| withself.assertRaisesRegex(OverflowError, "'data' is too large"): |
| cx.deserialize(b"b"*size) |
...however, it's never actually run, because it's skipped on machines with less than 24 Exabytes (!) of RAM:
test_deserialize_too_much_data_64bit (test.test_sqlite3.test_dbapi.SerializeTests.test_deserialize_too_much_data_64bit) ... skipped 'not enough memory: 25769803776.0G minimum needed'
(Found by running flake8 over Lib/ out of curiosity, see #93010 (comment))
Bug report
In a755124 (GH-26728, v3.11.0a7), @erlend-aasland added a
test_deserialize_too_much_data_64bit, which would instantly raise aNameErrorforsizeif run:cpython/Lib/test/test_sqlite3/test_dbapi.py
Lines 629 to 634 in b2694ab
...however, it's never actually run, because it's skipped on machines with less than 24 Exabytes (!) of RAM:
(Found by running
flake8overLib/out of curiosity, see #93010 (comment))