From: "Gábor Boskovits" <boskovits@gmail.com>
To: bw@inskydata.com
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Build failure on nss-3.36.1
Date: Sat, 3 Nov 2018 18:38:31 +0100 [thread overview]
Message-ID: <CAE4v=ph9YH_b13GJXxY_-Zg-YJPqPsbMFxZRHAt9UcXgGas9Lg@mail.gmail.com> (raw)
In-Reply-To: <3B8089BF-2CE3-428D-8623-F1E1661E8E6E@inskydata.com>
Hello,
Brian Woodcox <bw@inskydata.com> ezt írta (időpont: 2018. nov. 3., Szo, 18:29):
>
> I’m getting a build failure when building nss-3.36.1.
>
> I have the entire log. Here is the end part of it.
>
> Any ideas?
>
> Thanks.
>
> SUMMARY:
> ========
> NSS variables:
> --------------
> HOST=localhost
> DOMSUF=(none)
> BUILD_OPT=
> USE_X32=
> USE_64=1
> NSS_CYCLES=""
> NSS_TESTS=""
> NSS_SSL_TESTS="crl iopr policy"
> NSS_SSL_RUN="cov auth stapling stress"
> NSS_AIA_PATH=
> NSS_AIA_HTTP=
> NSS_AIA_OCSP=
> IOPR_HOSTADDR_LIST=
> PKITS_DATA=
> NSS_DISABLE_HW_AES=
> NSS_DISABLE_PCLMUL=
> NSS_DISABLE_AVX=
> NSS_DISABLE_ARM_NEON=
> NSS_DISABLE_SSSE3=
>
> Tests summary:
> --------------
> Passed: 52722
> Failed: 6
> Failed with core: 0
> ASan failures: 0
> Unknown status: 12
> TinderboxPrint:Unknown: 12
>
> Backtrace:
> 4 (primitive-load "/gnu/store/j2lm2bwnkndbw4vbv5ybfbs3yc6…")
> In ice-9/eval.scm:
> 191:35 3 (_ _)
> In srfi/srfi-1.scm:
> 640:9 2 (for-each #<procedure 9b6120 at /gnu/store/f95ghy8mx00…> …)
> In /gnu/store/f95ghy8mx00fc22nrvswvnpqlfdkf2nk-module-import/guix/build/gnu-build-system.scm:
> 799:31 1 (_ _)
> In /gnu/store/f95ghy8mx00fc22nrvswvnpqlfdkf2nk-module-import/guix/build/utils.scm:
> 616:6 0 (invoke _ . _)
>
> /gnu/store/f95ghy8mx00fc22nrvswvnpqlfdkf2nk-module-import/guix/build/utils.scm:616:6: In procedure invoke:
> Throw to key `srfi-34' with args `(#<condition &invoke-error [program: "./nss/tests/all.sh" arguments: () exit-status: 1 term-signal: #f stop-signal: #f] 68fd80>)'.
>
>
This is a test failure, could you try to build that again to see if it
fails consistently?
If it also fails for the second time, then please run guix build with
-K to keep the build directory, so we can have the test logs.
Thanks for the report.
Best regards,
g_bor
next prev parent reply other threads:[~2018-11-03 17:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-03 17:28 Build failure on nss-3.36.1 Brian Woodcox
2018-11-03 17:38 ` Gábor Boskovits [this message]
2018-11-03 17:47 ` Brian Woodcox
2018-11-03 19:38 ` Gábor Boskovits
2018-11-03 20:46 ` Björn Höfling
-- strict thread matches above, loose matches on Subject: below --
2018-11-04 3:17 Brian Woodcox
2018-11-04 3:46 ` Brian Woodcox
2018-11-04 10:38 ` Björn Höfling
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='CAE4v=ph9YH_b13GJXxY_-Zg-YJPqPsbMFxZRHAt9UcXgGas9Lg@mail.gmail.com' \
--to=boskovits@gmail.com \
--cc=bw@inskydata.com \
--cc=help-guix@gnu.org \
/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.