warning: build failed, waiting for other jobs to finish... ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop_plasma-j3-20210621-104403 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-11.1.0 * clang version 12.0.0 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/12/bin /usr/lib/llvm/12 12.0.0 Python 3.9.5 Available Rust versions: [1] rust-bin-1.53.0 * The following VMs are available for generation-2: *) AdoptOpenJDK 8.292_p10 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 system-vm The Glorious Glasgow Haskell Compilation System, version 8.10.4 HEAD of ::gentoo commit b5fb4b43d422c7f5a6ff7354c8b8b9b54d542119 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Thu Jun 24 22:36:30 2021 +0000 2021-06-24 22:36:29 UTC emerge -qpvO app-misc/rpick [ebuild N ] app-misc/rpick-0.8.4 USE="-debug"
Created attachment 719124 [details] emerge-info.txt
Created attachment 719127 [details] app-misc:rpick-0.8.4:20210624-231904.log
Created attachment 719130 [details] emerge-history.txt
Created attachment 719133 [details] environment
Created attachment 719136 [details] etc.portage.tar.bz2
Created attachment 719139 [details] temp.tar.bz2
Hi Toralf, I've not been able to reproduce this build failure. I've tested with these Rust versions/platforms: 0) dev-lang/rust-1.53.0:stable/1.53 from Gentoo. 1) dev-lang/rust-bin-1.53.0:stable/1.53 from Gentoo. 2) rust-1.53.0 from the Rust docker image. 3) rust-1.53.0-1.fc33.x86_64 from Fedora. In these cases, rpick has built without failure. Is the failure reproducible on your end? If so, I wonder what else might be different between our environments that might be a clue.
hhm, not reproducible, will close this therefore till a counterproof exists