From: Christopher Baines <mail@cbaines.net>
To: guix-devel@gnu.org
Cc: rb-general@lists.reproducible-builds.org,
Vagrant Cascadian <vagrant@reproducible-builds.org>
Subject: Re: [rb-general] Quick reproducible test for GNU Guix
Date: Wed, 12 Feb 2020 08:58:13 +0000 [thread overview]
Message-ID: <878sl818t6.fsf@cbaines.net> (raw)
In-Reply-To: <87k14t1967.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1183 bytes --]
Ludovic Courtès <ludo@gnu.org> writes:
>> Eventually, I'd like to do more systematic test of guix packages, with
>> published logs per-package, rather than whatever I happened to build on
>> the system so far, but this was a quick start to help flesh out ideas
>> for feature requests to "guix challenge" to make this all easier... more
>> on that soon!
>
> That’d be great!
>
> Related to that, Christopher Baines developed a nice feature for the
> Guix Data Service during and after the summit: for each Guix revision,
> there’s a page showing the overall package reproducibility status based
> on the info obtained from our two independent build farms. The URL is
> something like
> <http://data.guix.gnu.org/revision/e7ce4ef997c3db4d47d943c3e435f395b278bc50/package-reproducibility>
> (right now it’s empty for some reason, but normally it shows
> identical/different/inconclusive percentages.)
Hey,
This should be back working now. I changed how cross derivations are
stored and handled, and that broke this page. It's now back showing at
least something, but there's still some work to do before it's showing
representative data.
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 962 bytes --]
next prev parent reply other threads:[~2020-02-12 8:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 23:08 Quick reproducible test for GNU Guix Vagrant Cascadian
2020-02-11 14:38 ` [rb-general] " Ludovic Courtès
2020-02-12 8:58 ` Christopher Baines [this message]
2020-02-28 17:29 ` Holger Levsen
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=878sl818t6.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=guix-devel@gnu.org \
--cc=rb-general@lists.reproducible-builds.org \
--cc=vagrant@reproducible-builds.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 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.