From: Suhail Singh <suhailsingh247@gmail.com>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, "Ian Eure" <ian@retrospec.tv>,
guix-devel <guix-devel@gnu.org>
Subject: Re: Reducing "You found a bug" reports
Date: Mon, 22 Jul 2024 13:43:07 -0400 [thread overview]
Message-ID: <87h6ch2uhg.fsf@gmail.com> (raw)
In-Reply-To: <877cddhdeo.fsf@gmail.com> (Simon Tournier's message of "Mon, 22 Jul 2024 13:30:39 +0200")
Simon Tournier <zimon.toutoune@gmail.com> writes:
> More than often, the issue is transient, hard if not impossible to
> reproduce and thus hard to analyze. Even, when it happens for me,
> sometimes I say ok let try to collect some information for helping in
> debugging that but then just running again “guix pull” makes it pass.
Doesn't that suggest, that it may help to reword the below:
#+caption: <https://issues.guix.gnu.org/55066#0-lineno145>
#+begin_quote
guix pull: error: You found a bug: the program '/gnu/store/mpfp9nrzifhp3r5s3bv05b8xal5aa44f-compute-guix-derivation'
failed to compute the derivation for Guix (version: "e32cc011bbe899fda432906776702f74fa6b1450"; system: "x86_64-linux";
host version: "eb34ff16cc9038880e87e1a58a93331fca37ad92"; pull-version: 1).
Please report the COMPLETE output above by email to <bug-guix@gnu.org>.
#+end_quote
So that we encourage users to try a few times (perhaps possibly with
--fallback), and in case of repeat failures to then submit a bug report
to <bug-guix@gnu.org>. What about something like:
#+begin_example
guix pull: error: An error occurred: the program '/gnu/store/mpfp9nrzifhp3r5s3bv05b8xal5aa44f-compute-guix-derivation'
failed to compute the derivation for Guix (version: "e32cc011bbe899fda432906776702f74fa6b1450"; system: "x86_64-linux";
host version: "eb34ff16cc9038880e87e1a58a93331fca37ad92"; pull-version: 1).
Please try running "guix pull" again. In case of repeated failure,
please try passing "--fallback" to "guix pull". In case that still
doesn't resolve the error, please report the COMPLETE output above by
email to <bug-guix@gnu.org>.
#+end_example
I.e., perhaps the first step is simply to reword above so that we don't
recommend that users submit a bug report on their first (possibly
transient) failure.
--
Suhail
next prev parent reply other threads:[~2024-07-22 17:44 UTC|newest]
Thread overview: 12+ 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2024-07-23 20:45 Reducing "You found a bug" reports chris
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=87h6ch2uhg.fsf@gmail.com \
--to=suhailsingh247@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ian@retrospec.tv \
--cc=ludo@gnu.org \
--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.