From: "Bonface M. K." <bonfacemunyoki@gmail.com>
To: 44117@debbugs.gnu.org
Subject: bug#44117: Racket build fails
Date: Wed, 21 Oct 2020 19:51:18 +0300 [thread overview]
Message-ID: <86wnzjo73t.fsf@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1426 bytes --]
Hi guix. Building Racket on the tip: commit
5356cec68b9b7b5478d7df542c6a8fc70226b878
fails. The command used for build racket was:
--8<---------------cut here---------------start------------->8---
./pre-inst-env guix build racket
--8<---------------cut here---------------end--------------->8---
Here's the build log:
--8<---------------cut here---------------start------------->8---
Failed to build Racket with the error:
Ok: 93
Expected Fail: 0
Fail: 1
Unexpected Pass: 0
Skipped: 0
Timeout: 0
The output from the failed tests:
73/94 mesa:intel / anv_state_pool FAIL 0.42 s (killed by signal 11 SIGSEGV)
--- command ---
15:58:22 /tmp/guix-build-mesa-20.0.7.drv-0/build/src/intel/vulkan/state_pool
-------
Full log written to /tmp/guix-build-mesa-20.0.7.drv-0/build/meson-logs/testlog.txt
FAILED: meson-test
/gnu/store/rp1cmpqmwzxmsn6n6jrr9dm8ankl6ixv-meson-for-build-0.53.2/bin/meson test --no-rebuild --print-errorlogs
ninja: build stopped: subcommand failed.
command "ninja" "test" failed with status 1
--8<---------------cut here---------------end--------------->8---
--
Bonface M. K. <https://www.bonfacemunyoki.com>
Chief Emacs Bazu / Rieng ya software sare
Mchochezi of: <https://upbookclub.com> / Twitter: @BonfaceKilz
GPG Key: D4F09EB110177E03C28E2FE1F5BBAE1E0392253F
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 869 bytes --]
next reply other threads:[~2020-10-21 16:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 16:51 Bonface M. K. [this message]
2021-03-11 17:15 ` bug#44117: Racket no longer fails to build Jack Hill
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86wnzjo73t.fsf@gmail.com \
--to=bonfacemunyoki@gmail.com \
--cc=44117@debbugs.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).