From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?utf-8?Q?Ludovic_Court=C3=A8s?= <ludo@gnu.org>
Subject: Re: failing cuirass i686 tests
Date: Fri, 26 Jul 2019 00:48:19 +0200
Message-ID: <87pnlxrarw.fsf@gnu.org>
References: <9E629FBB-CF78-4D98-B087-03C3FB9F7C81@vllmrt.net>
 <87r26g4ska.fsf@devup.no>
 <C62D62C4-1CB9-43DA-B17A-ECF2AB3856E4@vllmrt.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:470:142:3::10]:55017)
 by lists.gnu.org with esmtp (Exim 4.86_2)
 (envelope-from <ludo@gnu.org>) id 1hqmX9-0002YZ-UB
 for guix-devel@gnu.org; Thu, 25 Jul 2019 18:48:24 -0400
In-Reply-To: <C62D62C4-1CB9-43DA-B17A-ECF2AB3856E4@vllmrt.net> (Robert
 Vollmert's message of "Thu, 25 Jul 2019 14:01:45 +0200")
List-Id: "Development of GNU Guix and the GNU System distribution."
 <guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
 <mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
 <mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Robert Vollmert <rob@vllmrt.net>
Cc: guix-devel@gnu.org

Hello,

Robert Vollmert <rob@vllmrt.net> skribis:

> Two updates here:
>
> 1. I=E2=80=99ve seen a similar failure on x86_64 now:
> http://ci.guix.gnu.org/build/1520368/details
> So it seems it=E2=80=99s not i686 specific, just fails more frequently th=
en.

Indeed, see also:

  https://ci.guix.gnu.org/search?query=3Dbasic+spec%3Aguix-master

> 2. The failing test "FAIL shell and user commands=E2=80=9D runs basic com=
mands
> 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 t=
he tests
> pass. My guess is therefore that it=E2=80=99s rather a problem with the t=
esting infrastructure
> rather than with that test specifically.

I found that this is quite reproducible like this:

  make check-system TESTS=3Dbasic
  guix build --check /gnu/store/=E2=80=A6-basic.drv
  # Try again until it fails.

I added a =E2=80=98pk=E2=80=99 and found that

  (marionette-eval (system "=E2=80=A6"))

returns 'ready when the test fails, as if it hadn=E2=80=99t received the 'r=
eady
message before (the one that we get when accessing the =E2=80=98repl=E2=80=
=99 field of
<marionette>).  I don=E2=80=99t see how that can happen, and why precisely =
here
and not in the previous or next test.  Thoughts?

Ludo=E2=80=99.