PASS: core PASS: openssl ERROR: u2f-server-test.sh ============================================================================ Testsuite summary for libu2f-server 1.0.1 ============================================================================ ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0_test_20171216-103216 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.2.0 * Available Python interpreters, in order of preference: [1] python3.5 [2] python3.6 (fallback) [3] python2.7 (fallback) [4] pypy3 (fallback) java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.6.0 [icedtea-bin-8] 2) JamVM JDK 2.0.0 [jamvm] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm [2] jamvm emerge -qpv app-crypt/libu2f-server [ebuild N ] app-crypt/libu2f-server-1.0.1 USE="-libressl -static-libs {-test}" ABI_X86="(64) -32 (-x32)"
Created attachment 511066 [details] emerge-info.txt
Created attachment 511068 [details] app-crypt:libu2f-server-1.0.1:20171220-040708.log
Created attachment 511070 [details] emerge-history.txt
Created attachment 511072 [details] environment
Created attachment 511074 [details] etc.portage.tbz2
Created attachment 511076 [details] logs.tbz2
Created attachment 511078 [details] temp.tbz2
Created attachment 511080 [details] tests.tbz2
I debugged this. The test-suite log file hasn't been attached to the bug but based on what I can reproduce, it's due to libu2f-server triggering some json-c assertion. The upstream simply suggests users to upgrade to 1.1.0 (See https://github.com/Yubico/pam-u2f/issues/93). Since 1.1.0 is stable, I'll remove 1.0.1 from the tree.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f8136943e6e72946c4d3884bea9d0ab5b4a9aef1 commit f8136943e6e72946c4d3884bea9d0ab5b4a9aef1 Author: Göktürk Yüksek <gokturk@gentoo.org> AuthorDate: 2019-06-05 19:22:12 +0000 Commit: Göktürk Yüksek <gokturk@gentoo.org> CommitDate: 2019-06-05 19:22:44 +0000 app-crypt/libu2f-server: remove old and now buggy 1.0.1 Bug: https://bugs.gentoo.org/641792 Bug: https://github.com/Yubico/pam-u2f/issues/93 Package-Manager: Portage-2.3.67, Repoman-2.3.12 Signed-off-by: Göktürk Yüksek <gokturk@gentoo.org> app-crypt/libu2f-server/Manifest | 1 - app-crypt/libu2f-server/libu2f-server-1.0.1.ebuild | 51 ---------------------- 2 files changed, 52 deletions(-)
(In reply to Göktürk Yüksek from comment #9) > I debugged this. The test-suite log file hasn't been attached to the bug but logs.tbz2 ?
(In reply to Toralf Förster from comment #11) > (In reply to Göktürk Yüksek from comment #9) > > I debugged this. The test-suite log file hasn't been attached to the bug but > logs.tbz2 ? I see that now, thanks. It may not be related to json-c but unfortunately the log file does not provide much information as to why it decided to exit with 99. It's just a series of u2f-server invocations one after another, all programmed to fail with 99 without telling you which line triggered the failure. When I debugged, I had to go in and insert a bunch of 'echo $LINENO' in there to see why it failed. Regardless of what we find, I don't see the upstream actually paying attention to it honestly.
