Description

MengAiDev

opened on Jul 22, 2025

Issue body actions

Bug report

Bug description:

When I clone cpython and use ./configure --disable-gil and make it, it got some warnings. After that I run make test, I found some test are failed. Here are two logs. (Does it means we should not use disable-gil??)
I noticed this at the beginning:

The necessary bits to build these optional modules were not found:
_dbm                  _decimal    

Core warnings:

Objects/typeobject.c:367:10: warning: ‘__atomic_load_4’ writing 4 bytes into a region of size 0 overflows the destination [-Wstringop-overflow=]
Python/crossinterp.c:367:10: warning: ‘__atomic_load_4’ writing 4 bytes into a region of size 0 overflows the destination [-Wstringop-overflow=]
Modules/_struct.c:367:10: warning: ‘__atomic_load_4’ writing 4 bytes into a region of size 0 overflows the destination [-Wstringop-overflow=]
Python/ceval.c:1912:38: warning: ‘stack_array’ may be used uninitialized [-Wmaybe-uninitialized]
Modules/_functoolsmodule.c:1575:16: warning: ‘result’ may be used uninitialized [-Wmaybe-uninitialized]

make.txt

make_test.txt

CPython versions tested on:

CPython main branch

Operating systems tested on:

Linux

Activity

1. MengAiDev

   added

   type-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error

   on Jul 22, 2025
2. ZeroIntensity commented on Jul 22, 2025

   

   ZeroIntensity

   on Jul 22, 2025

   Member

   More actions

   The atomics look like false positives, those always come up when compiling FT release builds. These should all disappear when compiling with --disable-gil --with-pydebug.

   Reacted by MQY
3. MengAiDev commented on Jul 22, 2025

   

   MengAiDev

   on Jul 22, 2025

   Author

   More actions

   The atomics look like false positives, those always come up when compiling FT release builds. These should all disappear when compiling with --disable-gil --with-pydebug.

   What about the test failed??
4. picnixz

   added

   testsTests in the Lib/test dirTests in the Lib/test dir

   pendingThe issue will be closed if no feedback is providedThe issue will be closed if no feedback is provided

   and removed

   type-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error

   on Jul 22, 2025
5. picnixz commented on Jul 22, 2025

   

   picnixz

   on Jul 22, 2025

   Member

   More actions

   This seems to be because you're running the CI tests via --fast-ci meant to be used by GHA. Have you tried just running ./python -m test -j12? the failures I see are failures that I've already seen during CI runs.

   I personally can't reproduce these failures except for test_warnings where something appeared to be wrong but the failure is just about environment having been changed so it's fine. But nothing about permissions issues or missing files. It could also be because of where the tests are being executed from.
6. MengAiDev commented on Jul 22, 2025

   

   MengAiDev

   on Jul 22, 2025

   Author

   More actions

   Thank you, I will close this issue.
7. MengAiDev

   closed this as completedon Jul 22, 2025
8. picnixz

   closed this as not plannedon Jul 22, 2025

Issue actions