From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: 宋文武 <iyzsong@envs.net>
Cc: Maxime Devos <maximedevos@telenet.be>,
65391@debbugs.gnu.org, guix-devel@gnu.org
Subject: Re: bug#65391: People need to report failing builds even though we have ci.guix.gnu.org for that
Date: Sat, 26 Aug 2023 23:39:54 -0400 [thread overview]
Message-ID: <87o7iti25x.fsf@gmail.com> (raw)
In-Reply-To: <871qfpxp76.fsf@envs.net> ("宋文武"'s message of "Sun, 27 Aug 2023 09:13:17 +0800")
Hi again,
宋文武 <iyzsong@envs.net> writes:
> Maxime Devos <maximedevos@telenet.be> writes:
>
>> For example, naev used to work just fine, yet apparently it doesn't
>> anymore: https://issues.guix.gnu.org/65390.
>>
>> Given that Guix has ci.guix.gnu.org, I would expect such new problems
>> to be detected and resolved early, and it was detected by
>> ci.guix.gnu.org, yet going by issues.guix.gnu.org it was never even
>> investigated.
>
> Yes, honestly I only look for build failures from bug reports, not from
> CI if i'm not doing a "request for merge" from another branch.
Another idea I had was we could add some feature to Cuirass where it'd
notify a team (by email) when a package under their scope has been
broken on the master branch.
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-08-27 3:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <295ef8c8-574a-4169-98f3-6d9aaeb773f1@telenet.be>
2023-08-27 1:13 ` bug#65391: People need to report failing builds even though we have ci.guix.gnu.org for that 宋文武
2023-08-27 3:38 ` Maxim Cournoyer
2023-08-27 3:39 ` Maxim Cournoyer [this message]
2023-08-27 4:30 ` Bruno Victal
2023-08-27 15:07 ` Giovanni Biscuolo
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=87o7iti25x.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=65391@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=iyzsong@envs.net \
--cc=maximedevos@telenet.be \
/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).