From: ludo@gnu.org (Ludovic Courtès)
To: Oleg Pykhalov <go.wigust@gmail.com>
Cc: 28694@debbugs.gnu.org
Subject: bug#28694: gnu: p11-kit: Update to 0.23.9 fails test.
Date: Wed, 04 Oct 2017 16:34:15 +0200 [thread overview]
Message-ID: <87vajv6kyg.fsf@gnu.org> (raw)
In-Reply-To: <87zi9739u6.fsf@gmail.com> (Oleg Pykhalov's message of "Wed, 04 Oct 2017 05:50:25 +0300")
Oleg Pykhalov <go.wigust@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’.
next prev parent reply other threads:[~2017-10-04 14:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 2:50 bug#28694: gnu: p11-kit: Update to 0.23.9 fails test Oleg Pykhalov
2017-10-04 6:21 ` Oleg Pykhalov
2017-10-04 14:34 ` Ludovic Courtès [this message]
2017-10-05 0:45 ` Oleg Pykhalov
2017-10-05 8:55 ` Ludovic Courtès
2017-10-06 4:32 ` Oleg Pykhalov
2017-10-06 6:42 ` Ludovic Courtès
2017-10-06 4:40 ` bug#28694: Status: " Oleg Pykhalov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vajv6kyg.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=28694@debbugs.gnu.org \
--cc=go.wigust@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.