From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?UTF-8?Q?G=C3=A1bor?= Boskovits <boskovits@gmail.com>
Subject: bug#33082: guix pull resulted in an error: compute-guix-derivation
Date: Tue, 30 Oct 2018 13:57:53 +0100
Message-ID: <CAE4v=pg2feYUnnP+g51PDPUSg-wTsG+S5V4ssB1skw-ukmjY0g@mail.gmail.com>
References: <8736t3713o.fsf@fastmail.com>
	<CAE4v=ph5cv0=8O9Jf+opT_y_n7kDjpHPyHGH9N7wUgEV8ROjNQ@mail.gmail.com>
	<877eiei9n2.fsf@gnu.org>
	<1539964762.2162108.1547911576.742F013B@webmail.messagingengine.com>
	<87k1mdrhhj.fsf@fastmail.com> <87o9bpaq4i.fsf@gnu.org>
	<878t2grdqb.fsf@fastmail.com>
	<CAE4v=pg0v5Seee0MMm=L9E42L2pKA3y8BC424w-erYPWw9BvWQ@mail.gmail.com>
	<87o9bbfv3x.fsf@fastmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Return-path: <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:40872)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gHTc6-00033n-Q5
	for bug-guix@gnu.org; Tue, 30 Oct 2018 08:59:23 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gHTbt-00015f-SE
	for bug-guix@gnu.org; Tue, 30 Oct 2018 08:59:13 -0400
Received: from debbugs.gnu.org ([208.118.235.43]:49252)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
	id 1gHTbq-000137-Ej
	for bug-guix@gnu.org; Tue, 30 Oct 2018 08:59:03 -0400
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gHTbp-0004O2-Vq
	for bug-guix@gnu.org; Tue, 30 Oct 2018 08:59:02 -0400
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.33082.B33082.154090429516809@debbugs.gnu.org>
In-Reply-To: <87o9bbfv3x.fsf@fastmail.com>
List-Id: Bug reports for GNU Guix <bug-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/bug-guix/>
List-Post: <mailto:bug-guix@gnu.org>
List-Help: <mailto:bug-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=subscribe>
Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org
Sender: "bug-Guix" <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
To: Joshua Branson <jbranso@fastmail.com>
Cc: 33082@debbugs.gnu.org

Hello Joshua,

Joshua Branson <jbranso@fastmail.com> ezt =C3=ADrta (id=C5=91pont: 2018. ok=
t.
30., K, 13:44):
>
> G=C3=A1bor Boskovits <boskovits@gmail.com> writes:
>
> > Joshua Branson <jbranso@fastmail.com> ezt =C3=ADrta (id=C5=91pont: 2018=
. okt. 29., H 15:54):
> >
> >  ludo@gnu.org (Ludovic Court=C3=A8s) writes:
> >
> >  > Hello,
> >  >
> >
> >  I was able to update successfully.  This bug seems like a duplicate of
> >  python 2 not deterministic.  Someone ought to close this bug report.
> >
> > I believe this is not the case, usually non deterministic means the bui=
ld is not reproducible, while this is a non-deterministic test failure. I w=
ould suggest
> > keeping this bug open, if I am right, maybe renaming to non-determinist=
ic test failure in python2. What do you think?
>
> Fair enough.  Since I made the bug report, then I should try to build it
> again and see what happens.
>

Thanks for having a look, please make sure to use guix build -K, so
that the failed build results are retained.
If you can't trigger the failure, then I will try to do this later.

Best regards,
g_bor