unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: guix-devel@gnu.org, zimoun <zimon.toutoune@gmail.com>,
	Muhammad Hassan <muhammad.hassan@uwaterloo.ca>,
	Guix Devel <guix-devel@gnu.org>
Subject: Re: Request to use GNU guix reproducibility bugs data for research project | University of Waterloo
Date: Tue, 02 Nov 2021 10:33:58 -0400	[thread overview]
Message-ID: <264E47F1-6985-4FDD-A9CF-5A68AB7FDAE3@lepiller.eu> (raw)
In-Reply-To: <86y266yde8.fsf@gmail.com>

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

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.

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.

Le 2 novembre 2021 08:01:51 GMT-04:00, zimoun <zimon.toutoune@gmail.com> a écrit :
>Hi,
>
>
>On Fri, 29 Oct 2021 at 16:48, Muhammad Hassan <muhammad.hassan@uwaterloo.ca> wrote:
>
>> I would like to scrap reproducibility bugs data from the linked
>> website to use in my research project that is being conducted at the
>> University of Waterloo. I am a Master's student.
>
>Nice!  Thank for your interest to Guix.
>
>
>> The project aims to provide automated support for non-reproducibility
>> detection.
>
>Non-reproducibility can be large. Against which one are you working?
>
>
>> Please tell me if there is an API that I can use to scrap the data.
>
>For instance, “guix build --no-substitutes” followed by “guix build
>--check” allows you to locally build and rebuild for checking if the
>build is reproducible – bitwise speaking.  Then, “guix challenge” allows
>to check your local builds against the build-farm.  Note that two
>build-farms are available [1,2] for various architectures.
>
>The Guix project runs a Data Service to collect various data. This
>service serves a JSON API (not-really documented but roaming on IRC
>#guix helps ;-)).  One year ago (already, damned!), a tiny and drafty
>script to somehow get the reproducibility coverage was around [3].  I
>have not worked on it since then and I do not know if it still works.
>Perhaps, it might be an entry-point for working on reproducibility data
>from Guix.
>
>Feel free to ask more details.
>
>
>1: <http://ci.guix.gnu.org/>
>2: <http://bordeaux.guix.gnu.org/>
>3: <https://lists.gnu.org/archive/html/guix-devel/2020-10/msg00181.html>
>
>
>Hope that helps,
>simon
>
>PS: I close the issue since it is not one, IIUC.  Instead, let redirect
>to the mailing list guix-devel which seems a better place for discussing
>such request. :-)
>
>

[-- Attachment #2: Type: text/html, Size: 3207 bytes --]

  reply	other threads:[~2021-11-02 15:03 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 [this message]
2021-11-03 20:06     ` Vagrant Cascadian

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=264E47F1-6985-4FDD-A9CF-5A68AB7FDAE3@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=guix-devel@gnu.org \
    --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).