------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop_gnome-j4_test-20230104-200049 ------------------------------------------------------------------- GNUMAKEFLAGS="$GNUMAKEFLAGS --jobserver-style=pipe" GNUMAKEFLAGS="$GNUMAKEFLAGS --shuffle" gcc-config -l: [1] x86_64-pc-linux-gnu-12 * clang/llvm (if any): clang version 15.0.6 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/15/bin Configuration file: /etc/clang/clang.cfg /usr/lib/llvm/15 15.0.6 Python 3.10.9 Available Rust versions: [1] rust-bin-1.66.0 * The following VMs are available for generation-2: 1) OpenJDK 17.0.5_p8 [openjdk-17] 2) Eclipse Temurin JDK 11.0.17_p8 [openjdk-bin-11] *) Eclipse Temurin JDK 17.0.5_p8 [openjdk-bin-17] 4) Eclipse Temurin JDK 8.352_p08 [openjdk-bin-8] 5) Eclipse Temurin JRE 17.0.5_p8 [openjdk-jre-bin-17] Available Java Virtual Machines: [1] openjdk-17 [2] openjdk-bin-8 [3] openjdk-bin-11 [4] openjdk-bin-17 system-vm [5] openjdk-jre-bin-17 php cli (if any): [1] php8.2 * HEAD of ::gentoo commit 068ec04caacdbd0fe391fdd0470fae9ce4e6372b Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Sat Jan 7 03:32:04 2023 +0000 2023-01-07 03:32:04 UTC emerge -qpvO app-admin/yadm [ebuild N ] app-admin/yadm-3.2.1 USE="-test"
Created attachment 847808 [details] emerge-info.txt
Created attachment 847810 [details] app-admin:yadm-3.2.1:20230107-052454.log
Created attachment 847812 [details] emerge-history.txt
Created attachment 847814 [details] etc.clang.tar.bz2
Created attachment 847816 [details] etc.portage.tar.bz2
Created attachment 847818 [details] temp.tar.bz2
Does the log really just cut off like that? Or does it hang?
I killed emerge so the log was therefore cut
3.2.2 looks to compile ok for me