-
-
Notifications
You must be signed in to change notification settings - Fork 30.4k
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
A lot of leaks in the test suite on the JIT
build
#120501
Comments
Oh, I'm sorry, this also happens on non-jit build (just a |
JIT
build
Uhm, sorry again 😄 It's actually related to JIT build. I cannot reproduce it in pure debug build anymore. But on the JIT build, I can. |
JIT
build
I'm not able to recreate this on Linux build on main - maybe Mac specific? (Well, a few skipped tests from missing extras, but not 300+ failures): ./make distclean && ./configure --enable-experimental-jit --with-pydebug && make -j8
./python -VV # Python 3.14.0a0 (heads/main:6af190f8d0, Jun 14 2024, 08:56:48) [GCC 11.4.0]
./python -m test -R 3:3 -j8
|
Interesting. I can reproduce this on both of my WSL and macOS setups. git clean -fdx && ./configure --with-pydebug --enable-experimental-jit && make -j && ./python.exe -m test -R 3:3 test___all__ |
Additionally, I can reproduce it on my Windows setup, using this command: pcbuild/build.bat -c Debug --experimental-jit ; ./python -m test -R 3:3 test___all__
...many lines of build logs
Running Debug|x64 interpreter...
Using random seed: 2230268839
0:00:00 Run 1 test sequentially in a single process
0:00:00 [1/1] test___all__
beginning 6 repetitions. Showing number of leaks (. for 0 or less, X for 10 or more)
123:456
XXX XXX
test___all__ leaked [11, 11, 11] references, sum=33
test___all__ leaked [11, 11, 11] memory blocks, sum=33
test___all__ failed (reference leak)
== Tests result: FAILURE ==
1 test failed:
test___all__
Total duration: 19.5 sec
Total tests: run=1
Total test files: run=1/1 failed=1
Result: FAILURE |
Agreed, I'm running the full windows tests on a native build now and seeing tons of leaking tests. I'll be curious if the failure list is the same as on your original Mac build or different. |
Just ran the Linux tests again sequentially (i.e. without |
Bisected to f6fab21 |
On Windows build, 314 tests failed:
|
I would like to test on my machine but it incorrectly assumes that I need clang-18 instead of gcc. I'm using OpenSUSE 15.5 and my clang is 15.0.7. How can I actually force to use the gcc for JIT? (and is there any support for it actually?) |
I think there's no support for gcc since our JIT is based on LLVM |
Oh, I thought that the JIT support explained in PEP 744 was for all Tier 1 platforms (especially "x86_64-unknown-linux-gnu/gcc") but I still need LLVM and Clang. Ok, I'll install local versions for that. |
@picnixz Actually we have a README for JIT, which is located at |
(Yes, I've seen the README after actually. I first looked at the PEP to see whether my platform was supported or not and was surprised) |
Is this rather new?
Log: https://github.com/sobolevn/cpython/actions/runs/10603373267/job/29387830804 |
I think it was #120713. |
Bug report
Bug description:
List of failed tests(I'm used
./python.exe -m test -R 3:3
to run the test suite):CPython versions tested on:
CPython main branch
Operating systems tested on:
macOS
Linked PRs
The text was updated successfully, but these errors were encountered: