From: Leo Famulari <leo@famulari.name>
To: Andreas Enge <andreas@enge.fr>,
"Christopher Baines via Development of GNU Guix and the GNU
System distribution." <guix-devel@gnu.org>
Cc: Christopher Baines <mail@cbaines.net>
Subject: Re: Comparison of branches on CI
Date: Thu, 30 Mar 2023 19:27:55 -0400 [thread overview]
Message-ID: <ZCYa+8b8BN+BIMqv@jasmine.lan> (raw)
In-Reply-To: <fc707e29-c49d-44f8-9937-fc7812260be2@app.fastmail.com>
On Thu, Mar 30, 2023 at 07:59:49AM -0400, Leo Famulari wrote:
> It is possible to use data.guix.gnu.org to create these comparisons. Sometimes it takes me a few minutes to remember how to do it, so the UI could grow some hints or "affordances". I'll provide an example later today, when I am near a computer.
Here is the page to use:
https://data.guix.gnu.org/compare/package-derivations?base_commit=d7673b49c086c898a8e749fd042081dc9d4631b8&target_commit=cf26ee1f99f84f817f96269541073846d546026b&build_change=broken&after_name=&limit_results=40
When comparing core-updates to master, the base commit should be from
the master branch, and the target commit should be from core-updates.
However, it looks like the Data Service doesn't know about these commits
on core-updates, which is unfortunate.
My understanding is that Cuirass stopped sending information to the Data
Service after this commit was deployed:
https://git.savannah.gnu.org/cgit/guix/guix-cuirass.git/commit/?id=e598f89445b58eede595e66076405931e6bb1e55
So, in the short term, to get useful information about core-updates from
the Data Service, we'd want to build core-updates in Bordeaux.
next prev parent reply other threads:[~2023-03-30 23:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 9:24 Comparison of branches on CI Andreas Enge
2023-03-30 11:59 ` Leo Famulari
2023-03-30 23:27 ` Leo Famulari [this message]
2023-03-31 8:51 ` Andreas Enge
2023-04-07 13:58 ` Andreas Enge
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=ZCYa+8b8BN+BIMqv@jasmine.lan \
--to=leo@famulari.name \
--cc=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=mail@cbaines.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).