GNU bug report logs -
#28694
gnu: p11-kit: Update to 0.23.9 fails test.
Previous Next
Reported by: Oleg Pykhalov <go.wigust <at> gmail.com>
Date: Wed, 4 Oct 2017 02:52:02 UTC
Severity: normal
Done: Oleg Pykhalov <go.wigust <at> gmail.com>
Bug is archived. No further changes may be made.
Full log
Message #11 received at 28694 <at> debbugs.gnu.org (full text, mbox):
Oleg Pykhalov <go.wigust <at> gmail.com> skribis:
> Latest p11-kit update fails to test and build.
>
> …
> FAIL: test-compat
> 1..2
> ok 1 /hash/murmur3
> ok 2 /hash/murmur3-incr
> …
> 1..16
> ok 1 /conf/test_parse_conf_1
> ok 2 /conf/test_parse_ignore_missing
> ok 3 /conf/test_parse_fail_missing
> ok 4 /conf/test_merge_defaults
> ok 5 /conf/test_load_globals_merge
> ok 6 /conf/test_load_globals_no_user
> ok 7 /conf/test_load_globals_system_sets_only
> ok 8 /conf/test_load_globals_user_sets_only
> ok 9 /conf/test_load_globals_system_sets_invalid
> ok 10 /conf/test_load_globals_user_sets_invalid
> ok 11 /conf/test_load_modules_merge
> ok 12 /conf/test_load_modules_no_user
> ok 13 /conf/test_load_modules_user_only
> ok 14 /conf/test_load_modules_user_none
> ok 15 /conf/test_parse_boolean
> not ok 16 /conf/setuid
> # assertion failed (ret == 18): (33 == 18)
> # in test_setuid() at test-conf.c:421
> FAIL: test-conf
> …
> 2 of 47 tests failed
Do the failures happen reproducibly for you? Is there a test log or
code giving a hint as to what is being tested and how it fails?
Thanks,
Ludo’.
This bug report was last modified 7 years and 291 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.