From: Suhail Singh <suhailsingh247@gmail.com>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: Ian Eure <ian@retrospec.tv>, guix-devel <guix-devel@gnu.org>
Subject: Re: toward a plan? (was Re: Reducing "You found a bug" reports)
Date: Tue, 10 Sep 2024 20:20:37 -0400 [thread overview]
Message-ID: <87y13z6nxm.fsf@gmail.com> (raw)
In-Reply-To: <87wmjjd0ki.fsf@gmail.com> (Simon Tournier's message of "Tue, 10 Sep 2024 16:51:09 +0200")
Simon Tournier <zimon.toutoune@gmail.com> writes:
> IMHO, the next actions are:
>
> a) Replace this message:
>
> (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>.~%"
>
> by something like: “sorry, could you try again guix pull --commit=~s
> and report if it fails again.”
That would be an improvement over current state, however ...
> 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?
I agree that this would be even better and IMHO we should implement b.
I.e., I think upon failure the message should:
1. recommend retrying at least once before submitting a bug report, and
2. should ensure submitted bug reports are as informative as possible.
--
Suhail
prev parent reply other threads:[~2024-09-11 0:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-09 3:04 Reducing "You found a bug" reports Ian Eure
2024-06-17 12:59 ` Ludovic Courtès
2024-06-17 16:09 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-06-17 20:40 ` Ricardo Wurmus
2024-07-22 20:48 ` Attila Lendvai
2024-07-17 18:24 ` Simon Tournier
2024-07-21 13:16 ` Ludovic Courtès
2024-07-22 11:30 ` Simon Tournier
2024-07-22 17:43 ` Suhail Singh
2024-09-10 14:51 ` toward a plan? (was Re: Reducing "You found a bug" reports) Simon Tournier
2024-09-11 0:20 ` Suhail Singh [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y13z6nxm.fsf@gmail.com \
--to=suhailsingh247@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ian@retrospec.tv \
--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.