| Summary: | dev-lang/python-3.13.0_beta1_p1 5 test failures | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | ktoupt |
| Component: | Current packages | Assignee: | Python Gentoo Team <python> |
| Status: | UNCONFIRMED --- | ||
| Severity: | normal | CC: | abulhair.saparov, ktoupt |
| Priority: | Normal | Keywords: | TESTFAILURE |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
build.log
emerge --info |
||
Created attachment 892748 [details]
emerge --info
I am also getting test failures which is preventing this package from emerging. The test failures are probably due to my optimization flags. However, I noticed that <python-3.13 would emerge fine, ignoring those test failures. From the ebuild, I can't see why 3.13 tests would have different behavior. Forgot to mention this is happening to me with dev-lang/python-3.13.0_beta1_p2 (In reply to Abulhair Saparov from comment #2) > I am also getting test failures which is preventing this package from > emerging. The test failures are probably due to my optimization flags. > However, I noticed that <python-3.13 would emerge fine, ignoring those test > failures. From the ebuild, I can't see why 3.13 tests would have different > behavior. You're almost certainly using USE=pgo. Upstream fixed/modified the behaviour for PGO to fail on failures. Ah yes it's because of pgo. Emerging with -pgo succeeds. Hmm, it seems like the profiling tests use system sqlite as well, so in order to use PGO I would need to add exceptions to optimization flags for both sqlite and python. |
Created attachment 892747 [details] build.log [ebuild NS ] dev-lang/python-3.13.0_beta1_p1 [3.11.9, 3.12.3] USE="ensurepip gdbm ncurses pgo readline sqlite ssl verify-sig -bluetooth -build -debug -examples -jit% -libedit -test -tk -valgrind" LLVM_SLOT="18%*" on a musl system