ERROR: gjs-tests - too few tests run (expected 99, got 15) ERROR: gjs-tests - exited with status 134 (terminated by signal 6?) FAIL: installed-tests/scripts/testCommandLine.sh 1 - System.exit(0) should exit successfully FAIL: installed-tests/scripts/testCommandLine.sh 2 - System.exit(42) should exit with the correct exit code PASS: installed-tests/scripts/testCommandLine.sh 3 - System.exit() should still exit across an FFI boundary FAIL: installed-tests/scripts/testCommandLine.sh 4 - --help should succeed ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 13.0-desktop-plasma-systemd_libressl_20170927-191034 ------------------------------------------------------------------- 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 gnome-extra/cjs [ebuild N ] gnome-extra/cjs-3.4.4 USE="cairo gtk -examples {-test}"
Created attachment 497546 [details] emerge-info.txt
Created attachment 497548 [details] emerge-history.txt
Created attachment 497550 [details] environment
Created attachment 497552 [details] etc.portage.tbz2
Created attachment 497554 [details] gnome-extra:cjs-3.4.4:20171003-181046.log
Created attachment 497556 [details] logs.tbz2
Created attachment 497558 [details] temp.tbz2
Can you please test if issue persists in 3.6.1?
where is 3.6.1 ? - The tinderbox usually uses the Gentoo repo
(In reply to Toralf Förster from comment #9) > where is 3.6.1 ? - The tinderbox usually uses the Gentoo repo https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ee69e19e11d86f3e097a248a51b67594641f0e36
(In reply to Toralf Förster from comment #9) Ah - repo synced a minute ago, but the results do not really differ : mr-fox / # grep FAIL /var/log/portage/gnome-extra:cjs-3.6.1:20171126-161233.log FAIL: installed-tests/scripts/testCommandLine.sh 1 - System.exit(0) should exit successfully FAIL: installed-tests/scripts/testCommandLine.sh 2 - System.exit(42) should exit with the correct exit code FAIL: installed-tests/scripts/testCommandLine.sh 4 - --help should succeed FAIL: installed-tests/scripts/testCommandLine.sh 5 - --help should print something FAIL: installed-tests/scripts/testCommandLine.sh 6 - should succeed when --help is not first arg FAIL: installed-tests/scripts/testCommandLine.sh 7 - should print something when --help is not first arg FAIL: installed-tests/scripts/testCommandLine.sh 8 - --help should succeed before a script file FAIL: installed-tests/scripts/testCommandLine.sh 9 - --help should print something before a script file FAIL: installed-tests/scripts/testCommandLine.sh 10 - --help should succeed before -c FAIL: installed-tests/scripts/testCommandLine.sh 11 - --help should print something before -c FAIL: installed-tests/scripts/testCommandLine.sh 12 - --help after script file should be passed to script FAIL: installed-tests/scripts/testCommandLine.sh 14 - --help after -c should be passed to script FAIL: installed-tests/scripts/testCommandLine.sh 16 - -I after script should succeed but give a warning FAIL: installed-tests/scripts/testCommandLine.sh 17 - --coverage-prefix after script should succeed but give a warning FAIL: installed-tests/scripts/testCommandLine.sh 18 - --coverage-output after script should succeed but give a warning FAIL: installed-tests/scripts/testCommandLine.sh 19 - --version should work FAIL: installed-tests/scripts/testCommandLine.sh 20 - --version should print something FAIL: installed-tests/scripts/testCommandLine.sh 21 - --version after -c should be passed to script FAIL: installed-tests/scripts/testWarnings.sh 1 - overwriting method with Signals.addSignalMethods() should warn FAIL: installed-tests/scripts/testWarnings.sh 2 - passing too many arguments to a GI function should warn FAIL: installed-tests/js/testSystem.js 2 System.version gives a plausible number # XFAIL: 0 # FAIL: 21
Indeed, had an issue with my package.env here, I can reproduce it locally now
This is fixed in https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8f947b8fa11d7a4e5532702da94249dd88e0d27b
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d9a6ddd6e85de8c752389a3b49118e9ac40658cc commit d9a6ddd6e85de8c752389a3b49118e9ac40658cc Author: Kristian Fiskerstrand <k_f@gentoo.org> AuthorDate: 2018-04-02 20:49:58 +0000 Commit: Kristian Fiskerstrand <k_f@gentoo.org> CommitDate: 2018-04-02 20:50:25 +0000 gnome-extra/cjs: Fix test failure on system.version check Bug: https://bugs.gentoo.org/633404 Package-Manager: Portage-2.3.24, Repoman-2.3.6 gnome-extra/cjs/cjs-3.6.1.ebuild | 2 ++ ...for-System.version-to-be-this-restrictive.patch | 25 ++++++++++++++++++++++ 2 files changed, 27 insertions(+)}
My bad, had forgotten to commit the patch in the previous push, the correct reference in previous comment.
