From: Maxime Devos <maximedevos@telenet.be>
To: "Ludovic Courtès" <ludo@gnu.org>,
"Pierre-Henry Fröhring" <contact@phfrohring.com>
Cc: 57039@debbugs.gnu.org
Subject: bug#57039: `make check' yields two failed tests.
Date: Tue, 9 Aug 2022 16:50:07 +0200 [thread overview]
Message-ID: <f984141e-a32e-1431-de17-59610bbfe4e6@telenet.be> (raw)
In-Reply-To: <87a68d7cfx.fsf@gnu.org>
[-- Attachment #1.1.1: Type: text/plain, Size: 1028 bytes --]
On 09-08-2022 15:50, Ludovic Courtès wrote:
> ;;; (fail (package (name "python-foo") (version "1.0.0") (source (origin (method url-fetch) (uri (pypi-uri "foo" version)) (sha256 (base32 "03ygiww1c9fdgs998x4rqhxa73gq0r30rp0vq50q022wp1d6w0cz")))) (build-system python-build-system) (propagated-inputs (list python-wrong)) (home-page"http://example.com") (synopsis "summary") (description "summary") (license license:lgpl2.0)) #f)
> test-name: pypi->guix-package, wheels
> location: /home/phf/src/guix/tests/pypi.scm:276
> source:
> + (test-assert
I think I've seen this one fail before in the past, but
non-deterministically, IIRC
> Not sure about that one. Does it still occur on current ‘master’?
It's a recent bug number and the submitter wrote they did "git checkout
..." and "git pull", so it looks like this happened on a current
master. Looking at git.savannah.gnu.org there haven't been changes in
this area, so I would think it's still effectively current master.
Greetings,
Maxime.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
prev parent reply other threads:[~2022-08-09 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-07 14:13 bug#57039: `make check' yields two failed tests Pierre-Henry Fröhring
2022-08-09 13:50 ` Ludovic Courtès
2022-08-09 14:44 ` Maxime Devos
2022-08-09 16:01 ` Ludovic Courtès
2022-08-09 14:50 ` Maxime Devos [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
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=f984141e-a32e-1431-de17-59610bbfe4e6@telenet.be \
--to=maximedevos@telenet.be \
--cc=57039@debbugs.gnu.org \
--cc=contact@phfrohring.com \
--cc=ludo@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).