GNU bug report logs - #65391
People need to report failing builds even though we have ci.guix.gnu.org for that

Previous Next

Package: guix;

Reported by: Maxime Devos <maximedevos <at> telenet.be>

Date: Sat, 19 Aug 2023 23:55:01 UTC

Severity: normal

Done: Andreas Enge <andreas <at> enge.fr>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Andreas Enge <andreas <at> enge.fr>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#65391: closed (People need to report failing builds even
 though we have ci.guix.gnu.org for that)
Date: Wed, 14 Feb 2024 09:15:01 +0000
[Message part 1 (text/plain, inline)]
Your message dated Wed, 14 Feb 2024 10:13:32 +0100
with message-id <ZcyEPIwweV0TPUJH <at> jurong>
and subject line Close
has caused the debbugs.gnu.org bug report #65391,
regarding People need to report failing builds even though we have ci.guix.gnu.org for that
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
65391: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=65391
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: Maxime Devos <maximedevos <at> telenet.be>
To: bug-guix <bug-guix <at> gnu.org>
Subject: People need to report failing builds even though we have
 ci.guix.gnu.org for that
Date: Sun, 20 Aug 2023 01:53:59 +0200
[Message part 3 (text/plain, inline)]
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, there is a delay, but that doesn't matter at all, as there's this 
dashboard <https://ci.guix.gnu.org/eval/668365/dashboard>.)

Do people really need to report 33% of all jobs 
(https://ci.guix.gnu.org/eval/668365/dashboard) before those failures 
are taken seriously, instead of the ‘there don't seem to be that much 
more build failures from the core-updates/... merge, let's solve them 
later (i.e., never)’ that seems to be  status quo?

Best regards,
Maxime Devos
[OpenPGP_0x49E3EE22191725EE.asc (application/pgp-keys, attachment)]
[OpenPGP_signature (application/pgp-signature, attachment)]
[Message part 6 (message/rfc822, inline)]
From: Andreas Enge <andreas <at> enge.fr>
To: 65391-done <at> debbugs.gnu.org
Subject: Close
Date: Wed, 14 Feb 2024 10:13:32 +0100
After reading through the first tenth of what seems to be an interesting
discussion and skimming through the remainder, I take the liberty to close
this bug. Such a discussion had better take place on guix-devel; the report
itself does not start with an actionable proposal: "People need to..."
looks more like an infinite task to me that cannot be closed as finished
if taken literally.

I understand that certain concrete proposals coming from the discussion
have been filed as separate issues, and would suggest that people
interested in the topic continue to do so.

Andreas



This bug report was last modified 1 year and 191 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.