From: Steve George <steve@futurile.net>
To: Christopher Baines <mail@cbaines.net>
Cc: 73515@debbugs.gnu.org
Subject: [bug#73515] Ready to merge qt-team branch?
Date: Mon, 11 Nov 2024 21:07:16 +0000 [thread overview]
Message-ID: <vthkxoiwovd5ph3kxwhcesvcn3il37hwroctv234inmqrdoie6@5stdlgcip2ty> (raw)
In-Reply-To: <87a5e5se7f.fsf@cbaines.net>
On 11 Nov, Christopher Baines wrote:
> Steve George <steve@futurile.net> writes:
(...)
> The QA data service has processed the tip of qt-team, that's how it's
> able to provide substitute information.
>
> Also, looks like it's based on 3dc63f8ca7af8d4fee32a03c206b571896a3a70a
> which is a few days old, so I'm guessing it was rebased a couple of days
> ago.
>
> The qa-frontpage has just finished canceling all the old builds that I
> guess were submitted prior to the rebase, so hopefully some builds will
> start happening soon.
>
> > I'm assuming this is partially why CI's substitutes available is so bad.
>
> I think CI has substitute availability comparable with master, which
> seems good to me at least regarding the merge of qt-team, it's bordeaux
> which is further behind.
Ah! thanks for the explanation Chris.
What's a reasonable level to wait for before a branch is merged? Master is at 96% on CI, and 92% on bordeaux right, so should we wait for the QT branch to get to the same point? And, is there a rule of thumb for the other architectures?
Steve
next prev parent reply other threads:[~2024-11-11 21:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-27 12:43 [bug#73515] Request for merging "qt-team" branch Z572
2024-11-11 18:01 ` [bug#73515] Ready to merge qt-team branch? Steve George
2024-11-11 20:33 ` Christopher Baines
2024-11-11 21:07 ` Steve George [this message]
2024-11-12 5:28 ` Z572
2024-11-21 14:37 ` [bug#73515] Request for merging "qt-team" branch Ludovic Courtès
2024-11-21 15:40 ` bug#73515: " Zheng Junjie
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=vthkxoiwovd5ph3kxwhcesvcn3il37hwroctv234inmqrdoie6@5stdlgcip2ty \
--to=steve@futurile.net \
--cc=73515@debbugs.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 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.