write ./gtk-3.0/gtk-contained-dark.css /usr/lib64/ruby/gems/2.2.0/gems/sass-3.5.3/lib/sass/cache_stores/base.rb:64: [BUG] Segmentation fault at 0x00000000000010 ruby 2.2.8p477 (2017-09-14 revision 59906) [x86_64-linux] -- Control frame information ----------------------------------------------- ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-hardened_libressl_20171207-183609 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.2.0 * Available Python interpreters, in order of preference: [1] python3.5 [2] python2.7 (fallback) [3] pypy (fallback) Available Ruby profiles: [1] ruby22 (with Rubygems) * java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.6.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpv x11-themes/greybird [ebuild N ] x11-themes/greybird-3.22.3 USE="-ayatana -gnome"
Created attachment 510112 [details] emerge-info.txt
Created attachment 510114 [details] emerge-history.txt
Created attachment 510116 [details] environment
Created attachment 510118 [details] etc.portage.tbz2
Created attachment 510120 [details] logs.tbz2
Created attachment 510122 [details] temp.tbz2
Created attachment 510124 [details] x11-themes:greybird-3.22.3:20171215-103552.log
Does this still happen with ruby 2.2.10?
yes, newer ruby is fine. But whilst I checked that I realized that emerging that package takes usually just 20-30 seconds except for systemd images, where it took 5 minutes: tinderbox@mr-fox ~ $ p=x11-themes/greybird ; (q=/tmp/q; for i in ~/*/*/var/log/emerge.log; do qlop --gauge --human --list --unlist -f $i $p > $q; if [[ -s $q ]]; then echo; echo $i; cat $q; fi; done; rm $q) /home/tinderbox/img1/17.0-desktop-plasma_20180218-101946/var/log/emerge.log Sat Feb 24 07:09:06 2018 >>> x11-themes/greybird-3.22.3 greybird: Sat Feb 24 07:08:36 2018: 30 seconds greybird: 1 times /home/tinderbox/img1/17.0-systemd_libressl-abi32+64_20180214-191118/var/log/emerge.log Fri Feb 16 17:48:45 2018 >>> x11-themes/greybird-3.22.3 greybird: Fri Feb 16 17:48:19 2018: 26 seconds greybird: 1 times /home/tinderbox/img2/17.0-desktop_libressl_20180403-174607/var/log/emerge.log Wed Apr 4 20:30:02 2018 >>> x11-themes/greybird-3.22.8 greybird: Wed Apr 4 20:29:38 2018: 24 seconds greybird: 1 times /home/tinderbox/img2/17.0-desktop-plasma-systemd_20180328-181735/var/log/emerge.log Tue Apr 3 06:41:25 2018 >>> x11-themes/greybird-3.22.8 greybird: Tue Apr 3 06:35:35 2018: 5 minutes, 50 seconds greybird: 1 times /home/tinderbox/img2/17.0-developer_20180402-130354/var/log/emerge.log Wed Apr 4 20:27:42 2018 >>> x11-themes/greybird-3.22.8 greybird: Wed Apr 4 20:27:15 2018: 27 seconds greybird: 1 times /home/tinderbox/run/17.0-desktop_libressl_20180403-174607/var/log/emerge.log Wed Apr 4 20:30:02 2018 >>> x11-themes/greybird-3.22.8 greybird: Wed Apr 4 20:29:38 2018: 24 seconds greybird: 1 times /home/tinderbox/run/17.0-desktop-plasma-systemd_20180328-181735/var/log/emerge.log Tue Apr 3 06:41:25 2018 >>> x11-themes/greybird-3.22.8 greybird: Tue Apr 3 06:35:35 2018: 5 minutes, 50 seconds greybird: 1 times /home/tinderbox/run/17.0-developer_20180402-130354/var/log/emerge.log Wed Apr 4 20:27:42 2018 >>> x11-themes/greybird-3.22.8 greybird: Wed Apr 4 20:27:15 2018: 27 seconds greybird: 1 times
ruby 2.2 is not in tree anymore, is this bug obsolete?
