From: Christopher Baines <mail@cbaines.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: zimoun <zimon.toutoune@gmail.com>, guix-devel@gnu.org
Subject: Re: ‘staging’ branch is open!
Date: Tue, 31 May 2022 08:34:40 +0100 [thread overview]
Message-ID: <878rqi87q9.fsf@cbaines.net> (raw)
In-Reply-To: <87bkvo46jt.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 862 bytes --]
Ludovic Courtès <ludo@gnu.org> writes:
> Hopefully we’ll get a clearer picture in the coming days…
There is starting to be some information in the QA data service instance:
https://data.qa.guix.gnu.org/compare-by-datetime/package-derivations?base_branch=master&base_datetime=&target_branch=staging&target_datetime=&system=x86_64-linux&target=none&build_change=broken&after_name=&limit_results=&all_results=on
That page should show things that build on master, but fail to build on
staging.
There are some false positives though, like python-protobuf that was
recently fixed on master and should be working on staging once master is
merged in.
There's probably some false negatives as well, since the build
information is coming from bordeaux.guix.gnu.org, and it's not yet
attempted to build everything for staging yet.
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next prev parent reply other threads:[~2022-05-31 7:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 23:08 ‘staging’ branch is open! Ludovic Courtès
2022-04-30 8:40 ` zimoun
2022-05-07 22:04 ` Ludovic Courtès
2022-05-08 20:14 ` zimoun
2022-05-15 20:55 ` Ludovic Courtès
2022-05-16 21:37 ` zimoun
2022-05-23 15:23 ` Ludovic Courtès
2022-05-31 7:34 ` Christopher Baines [this message]
2022-06-01 16:44 ` ‘staging’ to be merged soon: help needed! Ludovic Courtès
2022-05-03 17:54 ` ‘staging’ branch is open! Maxim Cournoyer
2022-05-10 12:59 ` python-cryptography and rust [was: Re: ‘staging’ branch is open!] Efraim Flashner
2022-05-15 21:22 ` Ludovic Courtès
2022-05-16 7:43 ` Efraim Flashner
2022-05-23 15:25 ` Ludovic Courtès
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=878rqi87q9.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--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).