From: Vagrant Cascadian <vagrant@reproducible-builds.org>
To: Julien Lepiller <julien@lepiller.eu>,
guix-devel@gnu.org, zimoun <zimon.toutoune@gmail.com>,
Muhammad Hassan <muhammad.hassan@uwaterloo.ca>
Subject: Re: Request to use GNU guix reproducibility bugs data for research project | University of Waterloo
Date: Wed, 03 Nov 2021 13:06:54 -0700 [thread overview]
Message-ID: <87zgqlvw9t.fsf@ponder> (raw)
In-Reply-To: <264E47F1-6985-4FDD-A9CF-5A68AB7FDAE3@lepiller.eu>
[-- Attachment #1: Type: text/plain, Size: 801 bytes --]
On 2021-11-02, Julien Lepiller wrote:
> The guix data service also has some info on reproducibility. See
> data.guix.gnu.org (Select master, the latest processed revision, and
> add /package-reproducibility to the URL). This page compares between
> berlin and bordeaux.
Thanks, just added a link at https://reproducible-builds.org/citests/
Been meaning to do that for ages...
> There are a lot of unknowns because the build farms haven't both built
> some of the packages, so we can't compare, but of those tgat have been
> built on both sites, we can already observe some interesting
> differences.
Yeah, the number of untestable packages looks a little low...
As of now, on x86_64:
Matching (7210, 34.76%)
Not matching (1748, 8.43%)
Unknown (11784, 56.81%)
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2021-11-03 20:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <YQBPR0101MB581397F18F7C0B3DD13AEFCE86879@YQBPR0101MB5813.CANPRD01.PROD.OUTLOOK.COM>
2021-11-02 12:01 ` Request to use GNU guix reproducibility bugs data for research project | University of Waterloo zimoun
2021-11-02 14:33 ` Julien Lepiller
2021-11-03 20:06 ` Vagrant Cascadian [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=87zgqlvw9t.fsf@ponder \
--to=vagrant@reproducible-builds.org \
--cc=guix-devel@gnu.org \
--cc=julien@lepiller.eu \
--cc=muhammad.hassan@uwaterloo.ca \
--cc=zimon.toutoune@gmail.com \
/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).