unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: Andy Tai <atai@atai.org>
Cc: guix-devel@gnu.org
Subject: Re: Guix QA: build status "unknown"
Date: Fri, 24 Mar 2023 08:37:53 +0000	[thread overview]
Message-ID: <874jqaee44.fsf@cbaines.net> (raw)
In-Reply-To: <CAJsg1E_ZBJG6xJMqqJLHa+=AZTNUXRYWm5YHPb63ru0uwT3=tA@mail.gmail.com>

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


Andy Tai <atai@atai.org> writes:

> I don't know if it is just me, but Guix QA recently seems to always
> show build status unknown when what really happens was the build
> succeeds on both x86-64 and aarch64 but on other platforms it was in
> "scheduled" state but the scheduled build never actually got run.   In
> any case thanks to the reviewers/committers some of my patches got
> reviewed and committed in this state.
>
> It is just the build status is misleading.   If just x86-64 and
> aarch64 builds are used to determine if a patch builds successfully
> then the badge should reflect such.

So, unfortunately it's not clear what the criteria are from the
interface, or why a particular status is shown.

However, currently armhf-linux builds [1] are also looked at as well
when considering the status, so this probably explains what you've been
seeing.

1: https://git.savannah.gnu.org/cgit/guix/qa-frontpage.git/tree/guix-qa-frontpage/issue.scm#n50

Currently only 1 of the 3 ARM build machines behind the bordeaux build
farm are operating, which is probably not helping get these builds done
in a timely manor.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]

      reply	other threads:[~2023-03-24 15:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-23 18:51 Guix QA: build status "unknown" Andy Tai
2023-03-24  8:37 ` Christopher Baines [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=874jqaee44.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=atai@atai.org \
    --cc=guix-devel@gnu.org \
    /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).