From: "Ludovic Courtès" <ludo@gnu.org>
To: Robert Vollmert <rob@vllmrt.net>
Cc: guix-devel@gnu.org
Subject: Re: failing cuirass i686 tests
Date: Fri, 26 Jul 2019 00:48:19 +0200 [thread overview]
Message-ID: <87pnlxrarw.fsf@gnu.org> (raw)
In-Reply-To: <C62D62C4-1CB9-43DA-B17A-ECF2AB3856E4@vllmrt.net> (Robert Vollmert's message of "Thu, 25 Jul 2019 14:01:45 +0200")
Hello,
Robert Vollmert <rob@vllmrt.net> skribis:
> Two updates here:
>
> 1. I’ve seen a similar failure on x86_64 now:
> http://ci.guix.gnu.org/build/1520368/details
> So it seems it’s not i686 specific, just fails more frequently then.
Indeed, see also:
https://ci.guix.gnu.org/search?query=basic+spec%3Aguix-master
> 2. The failing test "FAIL shell and user commands” runs basic commands
> guix/ls/grep/info. Judging by the test output, those do run successfully. The
> order of the output seems to be mixed up, but it looks the same as when the tests
> pass. My guess is therefore that it’s rather a problem with the testing infrastructure
> rather than with that test specifically.
I found that this is quite reproducible like this:
make check-system TESTS=basic
guix build --check /gnu/store/…-basic.drv
# Try again until it fails.
I added a ‘pk’ and found that
(marionette-eval (system "…"))
returns 'ready when the test fails, as if it hadn’t received the 'ready
message before (the one that we get when accessing the ‘repl’ field of
<marionette>). I don’t see how that can happen, and why precisely here
and not in the previous or next test. Thoughts?
Ludo’.
prev parent reply other threads:[~2019-07-25 22:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 15:43 failing cuirass i686 tests Robert Vollmert
2019-07-23 16:35 ` Marius Bakke
2019-07-25 12:01 ` Robert Vollmert
2019-07-25 22:48 ` Ludovic Courtès [this message]
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=87pnlxrarw.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=rob@vllmrt.net \
/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.