build warning and test failed with `--disable-gil`

[MengAiDev]

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

[ZeroIntensity]

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.

[MengAiDev]

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??

[picnixz]

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.

[MengAiDev]

Thank you, I will close this issue.