The futex facility returned an unexpected error code. error: could not compile `vec_map` Caused by: process didn't exit successfully: `rustc --crate-name vec_map /var/tmp/portage/app-misc/rpick-0.8.4/work/cargo_home/gentoo/vec_map-0.8.2/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C linker-plugin-lto -C metadata=27da588ee3b24fa1 -C extra-filename=-27da588ee3b24fa1 --out-dir /var/tmp/portage/app-misc/rpick-0.8.4/work/rpick-0.8.4/target/release/deps -L dependency=/var/tmp/portage/app-misc/rpick-0.8.4/work/rpick-0.8.4/target/release/deps --cap-lints allow` (exit status: 134) warning: build failed, waiting for other jobs to finish... ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_no_multilib-j3_debug-20210620-175917 ------------------------------------------------------------------- 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 Ruby profiles: [1] ruby26 (with Rubygems) [2] ruby30 (with Rubygems) * Available Rust versions: [1] rust-bin-1.53.0 * Available Java Virtual Machines: (none found) The Glorious Glasgow Haskell Compilation System, version 8.10.4 HEAD of ::gentoo commit cc3e0160f8a24a38b1d4624fd2ddd4bfdad6588f Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Sun Jun 27 06:36:31 2021 +0000 2021-06-27 06:36:30 UTC emerge -qpvO app-misc/rpick [ebuild N ] app-misc/rpick-0.8.4 USE="-debug"
Created attachment 719700 [details] emerge-info.txt
Created attachment 719703 [details] app-misc:rpick-0.8.4:20210628-071142.log
Created attachment 719706 [details] emerge-history.txt
Created attachment 719709 [details] environment
Created attachment 719712 [details] etc.portage.tar.bz2
Created attachment 719715 [details] temp.tar.bz2
Hi Toralf, This one has a similar error message to https://bugs.gentoo.org/798645, though on a different crate: The futex facility returned an unexpected error code. I am not able to reproduce this one either.
(In reply to Randy Barlow from comment #7) > Hi Toralf, > > This one has a similar error message to https://bugs.gentoo.org/798645, > though on a different crate: > > The futex facility returned an unexpected error code. > > I am not able to reproduce this one either. Hhm, but b/c this is a different image I do not think that both images are broken in the same way, rather the way of emerged packages or whatever else. Maybe -j3 is the reason ? jobs is currently set to "3" : RUST_TEST_THREADS=${jobs} RUST_TEST_TASKS=${jobs}
Hi Toralf! I have tried to reproduce this with MAKEOPTS=-j3, RUST_TEST_THREADS=3, and RUST_TEST_TASKS=3, but it builds for me. I don't usually set RUST_TEST_THREADS or RUST_TEST_TASKS, but I do usually use MAKEOPTS=-j8, -j4, and -j12 on three different systems and rpick build on all of those. Any other ideas on what might be happening?
fwiw I can't reproduce this either Only other times I seen these futex errors was in bugs like bug #801418, but it doesn't sound related (was caused by abi_x86_32 and CONFIG_COMPAT_32BIT_TIME being disabled in the kernel, but this is a no-multilib profile so I don't see how it could be involved -- I did try to build this on no-multilib, was fine too, not that I tried to change kernel.. but I'd believe the tinderbox has sane settings).
(In reply to Ionen Wolkens from comment #10) > fwiw I can't reproduce this either > > Only other times I seen these futex errors was in bugs like bug #801418, but > it doesn't sound related (was caused by abi_x86_32 and > CONFIG_COMPAT_32BIT_TIME being disabled in the kernel, but this is a > no-multilib profile so I don't see how it could be involved -- I did try to > build this on no-multilib, was fine too, not that I tried to change kernel.. > but I'd believe the tinderbox has sane settings). Hhm, it emerges fine here today at about 13 images - so it seems rather to be load problem with the tinderbox ? CONFIG_COMPAT_32BIT_TIME is set to "y" FWIW so I'll close this til it can be (reliable) be reproduced.
and looking at the affected image it emerged fin ean hour later: -rw-r--r-- 1 root root 26602 Jun 28 09:11 task.20210628-091159.app_misc_rpick.log -rw-r--r-- 1 root root 1062 Jun 28 10:01 task.20210628-100130.app_misc_rpick.log So either image specific or tinderbox had a hickup.
I guess(?) it could be some kind of race condition, although I never seen this kind before.
