all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 49913@debbugs.gnu.org,
	Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
Subject: bug#49913: python-networkx test failing
Date: Sun, 8 Aug 2021 13:54:10 +0300	[thread overview]
Message-ID: <YQ+30gkxn9yQ9nDT@3900XT> (raw)
In-Reply-To: <fa93ee83dc0bf86eb88ea0d93f98174767820100.camel@telenet.be>

[-- Attachment #1: Type: text/plain, Size: 964 bytes --]

On Sat, Aug 07, 2021 at 07:03:11PM +0200, Maxime Devos wrote:
> Hi,
> 
> > > networkx/algorithms/shortest_paths/tests/test_weighted.py:29: AssertionError
> > > =========== 1 failed, 3517 passed, 182 skipped in 246.61s (0:04:06) ============
> > > command "pytest" "-vv" "--pyargs" "networkx" failed with status 1
> > 
> > I've the following setup:
> > 
> > Host distribution: Parabola i686 with an x86_64 kernel (linux-libre-64)
> > Guix: Guix i686
> 
> I can reproduce on i686 (--system=i686-linux) but not x86_64.
> The test failure appears to be determenistic but architecture-dependent.
> 

Can you `guix pull` and test it again? I just updated it to 2.6.2 and
building with --system=i686-linux didn't show me any test errors.


-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-08-08 10:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-06 16:09 bug#49913: python-networkx test failing Denis 'GNUtoo' Carikli
2021-08-07 17:03 ` Maxime Devos
2021-08-08 10:54   ` Efraim Flashner [this message]
2021-08-08 16:20     ` Denis 'GNUtoo' Carikli
2021-08-08 16:51       ` Maxime Devos

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=YQ+30gkxn9yQ9nDT@3900XT \
    --to=efraim@flashner.co.il \
    --cc=49913@debbugs.gnu.org \
    --cc=GNUtoo@cyberdimension.org \
    --cc=maximedevos@telenet.be \
    /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.