From: Csepp <raingloom@riseup.net>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: "Maxim Cournoyer" <maxim.cournoyer@gmail.com>,
65391@debbugs.gnu.org, "Maxime Devos" <maximedevos@telenet.be>,
宋文武 <iyzsong@envs.net>, "Bruno Victal" <mirai@makinata.eu>,
"Andy Tai" <atai@atai.org>, Csepp <raingloom@riseup.net>
Subject: bug#65391: People need to report failing builds even though we have ci.guix.gnu.org for that
Date: Mon, 11 Sep 2023 09:28:32 +0200 [thread overview]
Message-ID: <cuc34zl6u64.fsf@riseup.net> (raw)
In-Reply-To: <87tts6kym3.fsf@gmail.com>
(changing the subject back to the intended one. I think the fact that
someone replies to an automated acknowledgement email like once a week
says indicates that the emails are not communicating clearly what their
purpose is. anyways, on to the actual issue at hand.)
Simon Tournier <zimon.toutoune@gmail.com> writes:
> Hi,
>
> On Tue, 29 Aug 2023 at 10:45, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
>
>> It's frustrating for users when a package is missing, but it's also
>> frustrating/inefficient for maintainers to stumble upon broken packages
>> when checking if an upgrade broke dependent packages (it takes time to
>> build them just to find out they fail, and researching they already
>> did), so a balance is needed.
>
> There is nothing worse as an user to have this experience:
>
> guix search foobar
>
> oh cool, foobar is there, let try it,
>
> guix shell foobar
>
> … wait …
> … stuff are building …
> … laptop is burning …
> … wait …
> Bang!
>
> Keeping broken packages is just annoyances. Contributor are annoyed
> because as said by the paragraph above. And user are annoyed as
> described just above.
>
> I am in favor to set a policy for removing then.
>
> The question is the way to detect them. QA can do whatever we want but
> until people are helping Chris because, IMHO, Chris is already enough
> busy to keep stuff running, we probably need to keep our process simple
> enough in order to stay actionable and avoid some vacuum of “coulda,
> shoulda or woulda”. For what my opinion is worth on that. :-)
>
> Cheers,
> simon
That is not a package problem but a Guix interface problem. I have been
saying for a while that there needs to be an option to disable all
non-trivial local builds by default when you know your machine can't
handle them.
Alternatively the CI could record some basic resource utilization
information, so users could for example set a limit on RAM. (Although
this gets tricky for parallel builds.)
next prev parent reply other threads:[~2023-09-11 7:34 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-19 23:53 bug#65391: People need to report failing builds even though we have ci.guix.gnu.org for that Maxime Devos
2023-08-22 23:45 ` Csepp
2023-08-24 9:57 ` Simon Tournier
2023-08-24 17:23 ` Csepp
2023-08-24 14:52 ` Maxime Devos
2023-08-24 17:27 ` Csepp
2023-08-29 22:52 ` Maxime Devos
2023-08-30 2:36 ` Maxim Cournoyer
2023-08-24 15:02 ` Maxime Devos
2023-08-24 17:38 ` Csepp
2023-08-27 1:13 ` 宋文武
2023-08-27 3:38 ` Maxim Cournoyer
2023-08-27 8:16 ` bug#65391: [Cuirass] feature requests for dashboard 宋文武 via Bug reports for GNU Guix
2023-08-27 3:39 ` bug#65391: People need to report failing builds even though we have ci.guix.gnu.org for that Maxim Cournoyer
2023-08-27 4:30 ` Bruno Victal
2023-08-27 15:07 ` Giovanni Biscuolo
2023-08-27 16:24 ` bug#65391: People need to report failing builds even Andy Tai
2023-08-27 21:26 ` Andy Tai
[not found] ` <handler.65391.B.169248925726403.ack@debbugs.gnu.org>
2023-08-29 14:03 ` bug#65391: Acknowledgement (People need to report failing builds even though we have ci.guix.gnu.org for that) Maxime Devos
2023-08-29 14:45 ` Maxim Cournoyer
2023-08-29 22:44 ` Maxime Devos
2023-08-30 2:28 ` Maxim Cournoyer
2023-08-30 10:39 ` Dr. Arne Babenhauserheide
2023-08-30 19:12 ` Maxim Cournoyer
2023-09-07 11:53 ` Simon Tournier
2023-09-11 8:30 ` Dr. Arne Babenhauserheide
2023-09-11 14:00 ` Simon Tournier
2023-09-11 23:12 ` Dr. Arne Babenhauserheide
2023-09-12 0:39 ` Simon Tournier
2023-08-30 11:50 ` Maxime Devos
2023-09-07 11:32 ` Simon Tournier
2023-09-11 7:28 ` Csepp [this message]
2023-09-11 7:58 ` bug#65391: People need to report failing builds even though we have ci.guix.gnu.org for that Simon Tournier
2023-09-11 21:52 ` Csepp
2023-09-12 18:43 ` bug#65391: Acknowledgement (People need to report failing builds even though we have ci.guix.gnu.org for that) Maxime Devos
2023-08-30 10:29 ` 宋文武 via Bug reports for GNU Guix
2024-02-14 9:13 ` bug#65391: Close Andreas Enge
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=cuc34zl6u64.fsf@riseup.net \
--to=raingloom@riseup.net \
--cc=65391@debbugs.gnu.org \
--cc=atai@atai.org \
--cc=iyzsong@envs.net \
--cc=maxim.cournoyer@gmail.com \
--cc=maximedevos@telenet.be \
--cc=mirai@makinata.eu \
--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 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.