From: Ricardo Wurmus <rekado@elephly.net>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: 36415@debbugs.gnu.org
Subject: [bug#36415] [PATCH] gnu: Add qlogo.
Date: Tue, 02 Jul 2019 10:50:45 +0200 [thread overview]
Message-ID: <878stgvmze.fsf@elephly.net> (raw)
In-Reply-To: <cu7tvc425qm.fsf@systemreboot.net>
Arun Isaac <arunisaac@systemreboot.net> writes:
>> I got this when running rounds=2:
>> The following builds are still in progress:
>> /gnu/store/yv7gjrplyym3arqi6qqiiqy3l4wzszp3-qlogo-0.92.drv
>> /gnu/store/ivln0c98vr9n8j25alx1dg1gbzpja11k-qtbase-5.11.3.drv
>> /gnu/store/ysv72wwn0gfjiqx2y4rxbf0gnhiv94yp-cups-2.2.11.drv
>> /gnu/store/mimhpwdwik9madwir21a2d0z6i1in7j0-cups-filters-1.23.0.drv
>> /gnu/store/syc8fwdl3mz2kxncd1k2mkqq4mslvxyv-qlogo-0.92.drv
>
> I get a similar message too.
>
>> I'm interpreting this as qlogo is not reproducible, no?
>
> I don't know. I have never understood how reproducibility checking works
> in Guix. Shouldn't --rounds=2 cause `guix build' to error out if there
> is some non-determinism?
Yes.
This might be a regression.
Build being reported as “in progress” is a feature. It’s used to
indicate remaining builds when more than one thing is being built.
In this case, though, it seems like a bug.
To test for reproducibility in this case you may want to use “--check”
after building the thing once.
--
Ricardo
next prev parent reply other threads:[~2019-07-02 8:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 8:03 [bug#36415] [PATCH] gnu: Add qlogo Arun Isaac
2019-06-28 16:35 ` swedebugia
2019-07-02 8:36 ` Arun Isaac
2019-07-02 8:50 ` Ricardo Wurmus [this message]
2019-07-04 17:11 ` Arun Isaac
2019-07-04 19:30 ` Ricardo Wurmus
2019-07-05 7:59 ` bug#36415: " Arun Isaac
2019-07-02 7:21 ` [bug#36415] " Efraim Flashner
2019-07-04 16:40 ` Arun Isaac
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=878stgvmze.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=36415@debbugs.gnu.org \
--cc=arunisaac@systemreboot.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 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).