[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: example of poor debugging message (follow up Guix Days)
From: |
45mg |
Subject: |
Re: example of poor debugging message (follow up Guix Days) |
Date: |
Mon, 24 Feb 2025 15:37:28 +0000 |
Ricardo Wurmus <rekado@elephly.net> writes:
> Speaking in very rough terms, the package definition is used to compile
> a builder script. The daemon runs that independent builder script,
> which has no reference and no knowledge of the module that provides the
> package definition.
Hmm, right.
For this specific example, it would probably be enough for the daemon to
print the name of the derivation that failed. IIRC, it usually does - if
I run `guix build buggy-package`, I usually get a line like 'build of
<hash>-buggy-package.drv failed' in the output. If it didn't do that
here then that's notable and it's worth investigating why. Or maybe the
backtrace Sharlatan gave us was part of a larger error?
- Re: example of poor debugging message (follow up Guix Days), (continued)
- Re: example of poor debugging message (follow up Guix Days), Sharlatan Hellseher, 2025/02/21
- Re: example of poor debugging message (follow up Guix Days), Simon Tournier, 2025/02/21
- Re: example of poor debugging message (follow up Guix Days), Ludovic Courtès, 2025/02/23
- Re: example of poor debugging message (follow up Guix Days), Ricardo Wurmus, 2025/02/23
- Re: example of poor debugging message (follow up Guix Days), Sharlatan Hellseher, 2025/02/23
- Re: example of poor debugging message (follow up Guix Days), 45mg, 2025/02/24
- Re: example of poor debugging message (follow up Guix Days), Ekaitz Zarraga, 2025/02/24
- Re: example of poor debugging message (follow up Guix Days), Ricardo Wurmus, 2025/02/24
- Re: example of poor debugging message (follow up Guix Days), Felix Lechner, 2025/02/24
- Re: example of poor debugging message (follow up Guix Days),
45mg <=
- Re: example of poor debugging message (follow up Guix Days), Andreas Enge, 2025/02/24
Message not available