Hi,
We have an issue! Worse, we have too many issues. :-)
Aside “guix pull” failures are annoying from user side, it’s burden on
developer side because some of us have to deal with them: Read, Answer
« transient and not a “real” bug » and Close.
Because yes, most of these reports are transient or hard to reproduce or
not actionable.
Andreas recently closed this list of “guix pull” bug error.
59940 closed
67035 closed
69465 closed
69473 closed
69710 closed
69757 closed
70075 closed
70297 closed
70646 closed
70650 closed
70651 closed
70658 closed
76713 closed
Look, previous data [1,2] below.
After looking at some of these 50+ reports, we have 3 classes of bugs:
1. transient
2. pulling from too old host revision
3. mix of both
IMHO, the next actions are:
a) Replace this message:
--8<---------------cut here---------------start------------->8---
(message (format #f "You found a bug: the program '~a'
failed to compute the derivation for Guix (version: ~s; system: ~s;
host version: ~s; pull-version: ~s).
Please report the COMPLETE output above by email to <~a>.~%"
--8<---------------cut here---------------end--------------->8---
by something like: “sorry, could you try again guix pull --commit=~s
and report if it fails again.”
b) Put here and there some logging [2] information. Patch#68946 [2]
provides logging facilities but is missing concrete user.
It could be worth to have it. So then, once “guix pull” fails, we
could ask to re-run “guix pull --commit=<target> --log-level=debug”.
This would help in having some information at failure time instead
of asking them after.
Moreover, it would provide information in order to diagnose all
these transient errors and see if they could be catched up instead
of erroring.
WDYT?
In all cases, feel free to pick one or more bugs from the list above and
investigate. Many do not have any answer – which is not welcoming and
friendly.
55066
58309 closed
61520 closed
62023 closed
62830
63451 closed
63830 closed
64489
64659 closed v1.4.0
64753 closed
64963 closed
65495 closed
65549 closed
65560 closed v1.4.0
66600 closed v1.4.0
67179 closed v1.2.0
67482 closed
67806 closed v1.4.0
67956 v1.2.0
67965 closed v1.4.0
68397 closed v1.4.0
69127 merged v1.4.0
69334 closed
69726 closed v1.3.0
70192
70200 v1.4.0
70201 v1.4.0
70649
70667
70681 v1.3.0
70940
71426
71437 v1.4.0
71691 v1.4.0
71908
71945
72028 v1.4.0
72100
72135 upgrade from v1.2.0
72332 v1.4.0
72353 v1.4.0
72563 v1.4.0
72639 v1.4.0
…to be continued…
Please note v1.4.0 means the host revision was v1.4.0.
Cheers,
simon
1: toward a plan? (was Re: Reducing "You found a bug" reports)
Simon Tournier <zimon.touto...@gmail.com>
Tue, 10 Sep 2024 16:51:09 +0200
id:87wmjjd0ki....@gmail.com
https://lists.gnu.org/archive/html/guix-devel/2024-09
https://yhetil.org/guix/87wmjjd0ki....@gmail.com
2: collection of “guix pull“ bug reports
Simon Tournier <zimon.touto...@gmail.com>
Wed, 23 Aug 2023 18:17:20 +0200
id:86jztl20of....@gmail.com
https://lists.gnu.org/archive/html/guix-devel/2023-08
https://yhetil.org/guix/86jztl20of....@gmail.com
3: [bug#68946] [RFC PATCH 0/1] Add logging capability to Guix
Maxim Cournoyer <maxim.courno...@gmail.com>
Mon, 05 Feb 2024 23:12:00 -0500
id:cover.1707192720.git.maxim.courno...@gmail.com
https://issues.guix.gnu.org/68946
https://issues.guix.gnu.org/msgid/cover.1707192720.git.maxim.courno...@gmail.com
https://yhetil.org/guix/cover.1707192720.git.maxim.courno...@gmail.com
