Repository navigation
test_zipfile64.[...].test_strip_removed_large_file_with_dd_no_sig fails on BigMem runs #152190
Copy link
Copy link
Closed
Closed
Copy link
Labels
testsTests in the Lib/test dirTests in the Lib/test dirtype-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error
Description
Activity
- addedtype-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or errortestsTests in the Lib/test dirTests in the Lib/test dir
on Jun 25, 2026 This is probably a side effect of the patch b6937c5, which increased the chunk size from 8 KiB to io.DEFAULT_BUFFER_SIZE (128 KiB on PC) for no-DD scan, while the allowed memory in
test_strip_removed_large_file_with_dd_no_sigremains 200 KiB.If we agree with the direction of keeping io.DEFAULT_BUFFER_SIZE chunk size, removing the overriding
allowed_memoryshould fix the test error:cpython/Lib/test/test_zipfile64.py
Line 204 in b6937c5
self.allowed_memory = 200*1024 - added 4 commits that reference this issue
on Jun 25, 2026 - Agreed.…On Thu, Jun 25, 2026, 6:17 AM Danny Lin ***@***.***> wrote: *danny0838* left a comment (python/cpython#152190) <#152190 (comment)> This is probably a side effect of the patch b6937c5 <b6937c5>, which increased the chunk size from 8 KiB to 1 MiB for no-DD scan, while the allowed memory in test_strip_removed_large_file_with_dd_no_sig remains 200 KiB. If we agree with the direction of keeping 1 MiB chunk size, removing the overriding allowed_memory should fix the test error: https://github.com/python/cpython/blob/b6937c5cf047ce98fe1233fefca2fb23f85bdd51/Lib/test/test_zipfile64.py#L204 — Reply to this email directly, view it on GitHub <#152190?email_source=notifications&email_token=AAAQXC2SVAE2DAX52WOZ7HL5BUQ5TA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINZZHE3DOOBZHA4KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4799678988>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAQXCZAF5HSJXS5EB3MLB35BUQ5TAVCNFSNUABEKJSXA33TNF2G64TZHM4DCNJZHA4TMMJ3JFZXG5LFHM2DONBTG42TCOBQGGQXMAQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>Reacted by Stan Ulbrych
- added 8 commits that reference this issue
on Jun 25, 2026 Fixed the error and tidied the code. Is there still any major concern about the PR? (There are test errors but seems irrelevant)
Confirmed this PR fixes the problem (MacOS and Linux). Can someone push this over the finish line?
Metadata
Metadata
Assignees
Labels
testsTests in the Lib/test dirTests in the Lib/test dirtype-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error
Projects
- StatusShow more project fieldsDone
Bug report
Bug description:
For example, in this run:
I'm also able to reproduce this locally:
This test was added recently in aec0aed by @danny0838 and @gpshead.
CPython versions tested on:
CPython main branch
Operating systems tested on:
No response
Linked PRs
test_zipfile64.py#152203