From: Simon Streit <simon@netpanic.org>
To: 50212@debbugs.gnu.org
Subject: bug#50212: Several tests fail, Bash fails often. Was: Tests fail while building Guix
Date: Fri, 27 Aug 2021 21:53:29 +0200 [thread overview]
Message-ID: <yguczpyhdfq.fsf@netpanic.org> (raw)
In-Reply-To: <ygu4kbcyt9d.fsf@netpanic.org> (Simon Streit's message of "Thu, 26 Aug 2021 20:07:26 +0200")
[-- Attachment #1: Type: text/plain, Size: 660 bytes --]
This is another follow up after having actually read the relevant info
section on how to do proper testing in Guix.
Checkout is at 5422920b9eaaa0c6bf779588748595c66ca86ba3, and this time I
prepared a test-suite.log with all errors that happen. Please find it
attached. This time it isn't too big either.
Unfortunately ‘tests/processes.scm’ hangs too, or remains unresponsive
after several minutes.
I really wonder what is making all the tests fail. I've tried building
the sources on different machines, or on clean user accounts. They all
fail in the same way. Has someone else been experiencing this yet?
Kind regards,
Simon
[-- Attachment #2: test-suite.log --]
[-- Type: application/octet-stream, Size: 879731 bytes --]
next prev parent reply other threads:[~2021-08-27 19:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <yguh7fcz5ee.fsf@netpanic.org>
2021-08-26 18:07 ` bug#50212: Tests fail while building Guix Simon Streit
2021-08-27 19:53 ` Simon Streit [this message]
2021-08-28 15:00 ` bug#50212: Several tests fail, Bash fails often. Was: " Maxime Devos
2021-08-28 18:13 ` Mark H Weaver
2021-08-28 22:14 ` Simon Streit
2021-08-28 22:32 ` Simon Streit
2021-08-29 13:06 ` Simon Streit
2021-08-29 21:28 ` Maxim Cournoyer
2021-08-30 18:17 ` Simon Streit
2021-08-30 20:24 ` Maxim Cournoyer
2021-08-28 15:33 ` bug#50212: " Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-08-28 21:56 ` Simon Streit
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=yguczpyhdfq.fsf@netpanic.org \
--to=simon@netpanic.org \
--cc=50212@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).