- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Testing work.hamcrest-0.1.0_p20160709: *** FAILED test case 28 of 42 *** ---------------------------------------------------- 2017-09-12 03:06:23.635 ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 13.0-desktop_libressl_20170903-100751 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-6.4.0 * llvm-config: 3.9.1 Available Python interpreters, in order of preference: [1] python3.4 [2] python2.7 (fallback) java-config: The following VMs are available for generation-2: 1) IcedTea JDK 7.2.6.11 [icedtea-bin-7] *) IcedTea JDK 3.5.1 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-7 [2] icedtea-bin-8 system-vm emerge -qpv dev-erlang/hamcrest [ebuild N ] dev-erlang/hamcrest-0.1.0_p20160709 USE="{-test}"
Created attachment 494094 [details] emerge-info.txt
Created attachment 494096 [details] dev-erlang:hamcrest-0.1.0_p20160709:20170912-010612.log
Created attachment 494098 [details] emerge-history.txt
Created attachment 494100 [details] environment
Created attachment 494102 [details] etc.portage.tbz2
Created attachment 494104 [details] logs.tbz2
Created attachment 494106 [details] temp.tbz2
I believe this and all similar bugs should be covered by the subslot changes to the rebar eclass that should make sure we always rebuild for the right erlang version.