make[2]: Entering directory '/var/tmp/portage/app-misc/jq-1.5-r3/work/jq-1.5' make[3]: Entering directory '/var/tmp/portage/app-misc/jq-1.5-r3/work/jq-1.5' FAIL: tests/mantest FAIL: tests/jqtest FAIL: tests/onigtest FAIL: tests/shtest ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 13.0-systemd_20170903-225953 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-6.4.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python2.7 (fallback) emerge -qpv app-misc/jq [ebuild N ] app-misc/jq-1.5-r3 USE="valgrind -oniguruma -static-libs {-test}"
Created attachment 493716 [details] emerge-info.txt
Created attachment 493718 [details] app-misc:jq-1.5-r3:20170910-123601.log
Created attachment 493720 [details] emerge-history.txt
Created attachment 493722 [details] environment
Created attachment 493724 [details] etc.portage.tbz2
Created attachment 493726 [details] logs.tbz2
Created attachment 493728 [details] temp.tbz2
Created attachment 493730 [details] tests.tbz2
Looking at test-suite.log [1] you have unconfigured valgrind. valgrind requires minimal debugging symbols for glibc to be available. It think it's usually done by setting FEATURES=nostrip for glibc and building glibc with CFLAGS+=-g valgrind: Fatal error at startup: a function redirection valgrind: which is mandatory for this platform-tool combination valgrind: cannot be set up. Details of the redirection are: valgrind: valgrind: A must-be-redirected function valgrind: whose name matches the pattern: strlen valgrind: in an object with soname matching: ld-linux-x86-64.so.2 valgrind: was not found whilst processing valgrind: symbols from the object with soname: ld-linux-x86-64.so.2 valgrind: valgrind: Possible fixes: (1, short term): install glibc's debuginfo valgrind: package on this machine. (2, longer term): ask the packagers valgrind: for your Linux distribution to please in future ship a non- valgrind: stripped ld.so (or whatever the dynamic linker .so is called) valgrind: that exports the above-named function using the standard valgrind: calling conventions for this platform. The package you need valgrind: to install for fix (1) is called valgrind: valgrind: On Debian, Ubuntu: libc6-dbg valgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo valgrind: valgrind: Note that if you are debugging a 32 bit process on a valgrind: 64 bit system, you will need a corresponding 32 bit debuginfo valgrind: package (e.g. libc6-dbg:i386). valgrind: valgrind: Cannot continue -- exiting now. Sorry.
(In reply to Sergei Trofimovich from comment #9) Ick, so no chance to avoid a test of this package by the ebuild if the prerequisites aren't met, right ? I can add that package with "notest" to https://github.com/toralf/tinderbox/blob/master/data/package.env.common in that case.
(In reply to Toralf Förster from comment #10) > (In reply to Sergei Trofimovich from comment #9) > Ick, so no chance to avoid a test of this package by the ebuild if the > prerequisites aren't met, right ? > > I can add that package with "notest" to > https://github.com/toralf/tinderbox/blob/master/data/package.env.common in > that case. For this particular package USE=-valgrind should still keep tests running but without trying to run them under valgrind. If you don't plan to build/install debugging libc for valgrind I'd suggest you to mask USE=valgrind useflag globally on tinderbox.
(In reply to Sergei Trofimovich from comment #11) ok, done : https://github.com/toralf/tinderbox/commit/10cc6722b2bd432441c7fb95aac29558237e7bb2
Thank you!
