* dev-python/flit-core : 3.12.0 >>> Source prepared. >>> Configuring source in /var/tmp/portage/dev-python/unittest-or-fail-2-r1/work/unittest-or-fail-2 ... >>> Source configured. >>> Compiling source in /var/tmp/portage/dev-python/unittest-or-fail-2-r1/work/unittest-or-fail-2 ... * python3_12: running distutils-r1_run_phase python_compile * ERROR: dev-python/unittest-or-fail-2-r1::gentoo failed (compile phase): * No wheel installed in python_compile(), did you call distutils-r1_python_compile? * ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 23.0_llvm-20250403-002508 Block bug #351559 if this looks like a parallel build issue. The attached etc.portage.tar.xz has all details. ------------------------------------------------------------------- GNUMAKEFLAGS="$GNUMAKEFLAGS --shuffle" gcc-config -l: [1] x86_64-pc-linux-gnu-14 * clang version 20.1.2+libcxx llvm-config: 20.1.2+libcxx Python 3.12.9 go version go1.24.1 linux/amd64 [1] php8.2 [2] php8.4 * Available Ruby profiles: [1] ruby32 (with Rubygems) [2] ruby33 (with Rubygems) * Available Rust versions: [1] rust-bin-1.85.1 [2] rust-1.85.1 [3] rust-bin-1.86 [4] rust-1.86 * The following VMs are available for generation-2: 1) Eclipse Temurin JDK 17.0.14_p7 [openjdk-bin-17] *) Eclipse Temurin JDK 21.0.6_p7 [openjdk-bin-21] 3) Eclipse Temurin JDK 8.442_p06 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 [2] openjdk-bin-17 [3] openjdk-bin-21 system-vm HEAD of ::gentoo commit 5322ff64c2e465234de7725e0bc1ec862ca6a29c Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Mon Apr 7 07:05:26 2025 +0000 2025-04-07 07:05:26 UTC emerge -qpvO =dev-python/unittest-or-fail-2-r1 [ebuild N ] dev-python/unittest-or-fail-2-r1 PYTHON_TARGETS="python3_12 -pypy3 -pypy3_11 -python3_10 -python3_11 -python3_13"
Created attachment 923808 [details] emerge-info.txt
Created attachment 923809 [details] dev-python:unittest-or-fail-2-r1:20250407-081053.log
Created attachment 923810 [details] emerge-history.txt
Created attachment 923811 [details] environment
Created attachment 923812 [details] etc.clang.tar.xz
Created attachment 923813 [details] etc.portage.tar.xz
Created attachment 923814 [details] qlist-info.txt.xz
Created attachment 923815 [details] temp.tar.xz
Was it pulled as a dependency or directly?
(In reply to Michał Górny from comment #9) > Was it pulled as a dependency or directly? Mon Apr 7 08:10:40 -00 2025 dev-python/unittest-or-fail These are the packages that would be merged, in reverse order: Calculating dependencies . .... done! Dependency resolution took 11.74 s (backtrack: 0/20). [ebuild N ] dev-python/unittest-or-fail-2-r1::gentoo PYTHON_TARGETS="python3_12 -pypy3 -pypy3_11 -python3_10 -python3_11 -python3_13" 0 KiB Total: 1 package (1 new), Size of downloads: 0 KiB >>> Verifying ebuild manifests Side note: It is a good question. Maybe I should attach the task log of the emerge process too to a bug report?
OT: I do not understand, why the current task is not in the attached emerge history, but it should be there: https://github.com/toralf/tinderbox/blob/main/bin/job.sh#L1200
This broke with: commit 67f008f6acc086e0a58dfebd1b019bcdad73620a Author: Michał Górny <mgorny@gentoo.org> Date: Wed Mar 26 12:32:32 2025 +0100 distutils-r1.eclass: Add a safety check for wheel install done Add a safety check to verify that distutils_wheel_install is being (usually indirectly) called in python_compile(), when using PEP517 build. If it weren't, this usually indicates that distutils-r1_python_compile (or distutils_pep517_install) was not called. Signed-off-by: Michał Górny <mgorny@gentoo.org> Closes: https://github.com/gentoo/gentoo/pull/41222 Signed-off-by: Michał Górny <mgorny@gentoo.org> because in unittest-or-fail, we do: python_compile() { if has "${EPYTHON/./_}" "${PYTHON_USED[@]}"; then distutils-r1_python_compile fi } [...] python_install() { if has "${EPYTHON/./_}" "${PYTHON_USED[@]}"; then distutils-r1_python_install fi }
And we're only doing that to workaround pkgcheck limitations (otherwise it would consider packages depending on unittest-or-fail unsuitable for PythonCompatUpdate). Maybe I'll just add a REQUIRED_USE in there. It's not like there's any point in having this installed for py3.12+ only.
Or maybe we can last rite it entirely. In the end, the purpose was to catch packages with wrong unittest calls — but given that py3.12+ doesn't need it, and py3.12+ testing will catch wrong unittest calls, I suppose we don't really need it anymore.
I think it makes sense to kill it, yeah.
