Pjotr Prins writes:
>> So I ran
>>
>>guix build --log-file
>> /gnu/store/wk9qbhmdzs62mp40casrndcgm3p50m3b-diamond-0.9.22.drv
>>
>> which gave me
>>
>>
>> /var/log/guix/drvs/wk/9qbhmdzs62mp40casrndcgm3p50m3b-diamond-0.9.22.drv.bz2
>>
>> which contains the build log for this failed build
> So I ran
>
>guix build --log-file
> /gnu/store/wk9qbhmdzs62mp40casrndcgm3p50m3b-diamond-0.9.22.drv
>
> which gave me
>
>/var/log/guix/drvs/wk/9qbhmdzs62mp40casrndcgm3p50m3b-diamond-0.9.22.drv.bz2
>
> which contains the build log for this failed build, including the "foo"
> error mess
Hi Tobias,
> Ricardo Wurmus wrote:
>> Note that the patch cannot be applied because I had to change how “@
>> build-failed” is treated. The underlying problem here is that the
>> daemon may send a multi-line message through the port, which
>> unfortunately doesn’t necessarily arrive in one piec
Ricardo,
[And apologies for another empty mail, everyone.]
Ricardo Wurmus wrote:
Note that the patch cannot be applied because I had to change
how “@
build-failed” is treated. The underlying problem here is that
the
daemon may send a multi-line message through the port, which
unfortunately d
Ricardo Wurmus wrote:
Hi,
What about immediately giving the file name of the log, as with
the
patch attached? Several people have already mentioned not
knowing about
‘guix build --log-file’ so this would probably be helpful.
This would be fine.
Note that the patch cannot be applied becaus
Hi,
> What about immediately giving the file name of the log, as with the
> patch attached? Several people have already mentioned not knowing about
> ‘guix build --log-file’ so this would probably be helpful.
This would be fine.
Note that the patch cannot be applied because I had to change ho
Hello,
Ricardo Wurmus skribis:
>> On latest
>>
>> ./pre-inst guix package -i something
>>
>> The new color scheme is nice for output. But I miss the old build
>> logs. How do I get them back?
>
> The build logs are stored by the daemon. You can get their location by
> doing
>
> guix build
On Wed, Sep 12, 2018 at 08:52:36AM +0200, Ricardo Wurmus wrote:
> It does seem to work. To test this I added (error "foo") to a build
> phase in the “diamond” package and ran
>
>guix package -i diamond
>
> This ends with
>
>Build failed:
> /gnu/store/wk9qbhmdzs62mp40casrndcgm3p50m3b-d
Hi Danny,
> On Tue, 11 Sep 2018 13:52:16 +0200
> Ricardo Wurmus wrote:
>
>> The build logs are stored by the daemon. You can get their location by
>> doing
>>
>> guix build --log-file something
>
> Does this also work for failed builds - without rebuilding it again?
It does seem to work.
Hi Ricardo,
On Tue, 11 Sep 2018 13:52:16 +0200
Ricardo Wurmus wrote:
> The build logs are stored by the daemon. You can get their location by
> doing
>
> guix build --log-file something
Does this also work for failed builds - without rebuilding it again?
pgpJ9_EeqYaBB.pgp
Description: O
Pierre Neidhardt transcribed 1.3K bytes:
>
> > Also, on build failure, it would be nice to print a hint on what to
> > invoke to get to the failed build log after all (guix-daemon still wrote
> > it).
>
> Indeed. Is there such a command?
>
> What about adding a hint, for instance:
>
> Buildin
Hi Pjotr,
> On latest
>
> ./pre-inst guix package -i something
>
> The new color scheme is nice for output. But I miss the old build
> logs. How do I get them back?
The build logs are stored by the daemon. You can get their location by
doing
guix build --log-file something
Note also th
> Also, on build failure, it would be nice to print a hint on what to
> invoke to get to the failed build log after all (guix-daemon still wrote
> it).
Indeed. Is there such a command?
What about adding a hint, for instance:
Building /gnu/store/i0kxn9cpkw8ml5472s185kxa6n64kmir-webkitgtk-2.20.
Hi Pjotr,
On Tue, 11 Sep 2018 11:04:25 +0200
Pjotr Prins wrote:
> Ah, the --verbose switch helps. Still I think the hash and -K should
> be displayed by default.
I agree.
Also, on build failure, it would be nice to print a hint on what to
invoke to get to the failed build log after all (guix-d
Ah, the --verbose switch helps. Still I think the hash and -K should
be displayed by default.
On Tue, Sep 11, 2018 at 10:26:53AM +0200, Pjotr Prins wrote:
> On latest
>
> ./pre-inst guix package -i something
>
> The new color scheme is nice for output. But I miss the old build
> logs. How do I
On latest
./pre-inst guix package -i something
The new color scheme is nice for output. But I miss the old build
logs. How do I get them back? Trying different verbosity levels does
not help.
Also when I got the hash wrong I did not display the new hash value.
And -K does not show the tmp loca
16 matches
Mail list logo
