'core-updates' status

'core-updates' status

[Marius Bakke]

[-- Attachment #1: Type: text/plain, Size: 638 bytes --]

Hello!

'core-updates' has finished building on x86_64 and i686.  There are a
few failing packages still, but nothing too scary.  Please try to fix
some if you can!

https://hydra.gnu.org/eval/109753?full=1&compare=master#tabs-now-fail

Most of the "dependency failed" armhf packages are because Hydra
believes 'bluez' is failing, even though it has built successfully
twice:

https://hydra.gnu.org/job/gnu/core-updates/bluez-5.45.armhf-linux

What do you think, are we ready to merge this branch?  There are ~2k
armhf packages left in the queue, but many of them have already changed
in 'master' and thus will need to be rebuilt anyway.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

Re: 'core-updates' status

[Ben Woodcroft]

Hi Marius,


On 19/08/17 07:24, Marius Bakke wrote:
> Hello!
>
> 'core-updates' has finished building on x86_64 and i686.  There are a
> few failing packages still, but nothing too scary.  Please try to fix
> some if you can!
I went to look at blast+ on armhf, and came across this:

/tmp/guix-build-blast+-2.6.0.drv-0/ncbi-blast-2.6.0+-src/c++/include/corelib/ncbistl.hpp:73:23: fatal error: error writing to /tmp/guix-build-blast+-2.6.0.drv-0/ccWOjvYh.s: No space left on device

Is this symptomatic of a larger issue?

ben

Re: 'core-updates' status

[Mark H Weaver]

Ben Woodcroft <b.woodcroft@uq.edu.au> writes:

> I went to look at blast+ on armhf, and came across this:
>
> /tmp/guix-build-blast+-2.6.0.drv-0/ncbi-blast-2.6.0+-src/c++/include/corelib/ncbistl.hpp:73:23:
> fatal error: error writing to
> /tmp/guix-build-blast+-2.6.0.drv-0/ccWOjvYh.s: No space left on device
>
> Is this symptomatic of a larger issue?

No.  One of the armhf build slaves ran out of disk space recently.  It's
fixed now, and I tried to restart most of the failed builds, but I guess
this one slipped through the cracks.  I'll restart it.

    Thanks,
      Mark

Re: 'core-updates' status

[Christopher Baines]

[-- Attachment #1: Type: text/plain, Size: 672 bytes --]

On Fri, 18 Aug 2017 23:24:29 +0200
Marius Bakke <mbakke@fastmail.com> wrote:

> 'core-updates' has finished building on x86_64 and i686.  There are a
> few failing packages still, but nothing too scary.  Please try to fix
> some if you can!
> 
> https://hydra.gnu.org/eval/109753?full=1&compare=master#tabs-now-fail

So I spotted [1] that the tailon system test is failing, but the way
that it failed isn't included in the log. Is there a way to get at the
log file which it generates, or, would it be good to modify the system
tests to print out the log file when the test ends?

1:
https://hydra.gnu.org/job/gnu/core-updates/test.tailon.x86_64-linux/all

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 963 bytes --]

Re: 'core-updates' status

[Ludovic Courtès]

Christopher Baines <mail@cbaines.net> skribis:

> On Fri, 18 Aug 2017 23:24:29 +0200
> Marius Bakke <mbakke@fastmail.com> wrote:
>
>> 'core-updates' has finished building on x86_64 and i686.  There are a
>> few failing packages still, but nothing too scary.  Please try to fix
>> some if you can!
>> 
>> https://hydra.gnu.org/eval/109753?full=1&compare=master#tabs-now-fail
>
> So I spotted [1] that the tailon system test is failing, but the way
> that it failed isn't included in the log. Is there a way to get at the
> log file which it generates, or, would it be good to modify the system
> tests to print out the log file when the test ends?

We could print the log upon failure, indeed.

In the meantime, perhaps you can reproduce it on your machine?  :-)

Thanks,
Ludo’.

Re: 'core-updates' status

[Christopher Baines]

[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]

On Tue, 22 Aug 2017 10:34:45 +0200
ludo@gnu.org (Ludovic Courtès) wrote:

> Christopher Baines <mail@cbaines.net> skribis:
> 
> > On Fri, 18 Aug 2017 23:24:29 +0200
> > Marius Bakke <mbakke@fastmail.com> wrote:
> >  
> >> 'core-updates' has finished building on x86_64 and i686.  There
> >> are a few failing packages still, but nothing too scary.  Please
> >> try to fix some if you can!
> >> 
> >> https://hydra.gnu.org/eval/109753?full=1&compare=master#tabs-now-fail  
> >
> > So I spotted [1] that the tailon system test is failing, but the way
> > that it failed isn't included in the log. Is there a way to get at
> > the log file which it generates, or, would it be good to modify the
> > system tests to print out the log file when the test ends?  
> 
> We could print the log upon failure, indeed.
> 
> In the meantime, perhaps you can reproduce it on your machine?  :-)

Unfortunately not, it passes when I run it locally. I can see the test
it fails on, which does involve waiting for the service to start, and
it waits for up to 50 seconds, but maybe that isn't enough, it could
also be a different failure though.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 963 bytes --]

Re: 'core-updates' status

[Ludovic Courtès]

Christopher Baines <mail@cbaines.net> skribis:

> On Tue, 22 Aug 2017 10:34:45 +0200
> ludo@gnu.org (Ludovic Courtès) wrote:
>
>> Christopher Baines <mail@cbaines.net> skribis:
>> 
>> > On Fri, 18 Aug 2017 23:24:29 +0200
>> > Marius Bakke <mbakke@fastmail.com> wrote:
>> >  
>> >> 'core-updates' has finished building on x86_64 and i686.  There
>> >> are a few failing packages still, but nothing too scary.  Please
>> >> try to fix some if you can!
>> >> 
>> >> https://hydra.gnu.org/eval/109753?full=1&compare=master#tabs-now-fail  
>> >
>> > So I spotted [1] that the tailon system test is failing, but the way
>> > that it failed isn't included in the log. Is there a way to get at
>> > the log file which it generates, or, would it be good to modify the
>> > system tests to print out the log file when the test ends?  
>> 
>> We could print the log upon failure, indeed.
>> 
>> In the meantime, perhaps you can reproduce it on your machine?  :-)
>
> Unfortunately not, it passes when I run it locally. I can see the test
> it fails on, which does involve waiting for the service to start, and
> it waits for up to 50 seconds, but maybe that isn't enough, it could
> also be a different failure though.

OK.  Maybe you could try locally to:

  guix build --check ….drv --rounds=10 -K

or something.

It doesn’t sound like a blocker anyway.

Thanks,
Ludo’.

Re: 'core-updates' status

[Efraim Flashner]

[-- Attachment #1: Type: text/plain, Size: 2050 bytes --]

On Fri, Aug 18, 2017 at 11:24:29PM +0200, Marius Bakke wrote:
> Hello!
> 
> 'core-updates' has finished building on x86_64 and i686.  There are a
> few failing packages still, but nothing too scary.  Please try to fix
> some if you can!
> 
> https://hydra.gnu.org/eval/109753?full=1&compare=master#tabs-now-fail
> 
> Most of the "dependency failed" armhf packages are because Hydra
> believes 'bluez' is failing, even though it has built successfully
> twice:
> 
> https://hydra.gnu.org/job/gnu/core-updates/bluez-5.45.armhf-linux
> 
> What do you think, are we ready to merge this branch?  There are ~2k
> armhf packages left in the queue, but many of them have already changed
> in 'master' and thus will need to be rebuilt anyway.

I yesterday had weechat fail to graft on core-updates:

The following derivation will be built:
   /gnu/store/9yp5dgijz8d09rm8v45lp7iwbjdmxfk5-weechat-1.9.drv
@ build-started /gnu/store/9yp5dgijz8d09rm8v45lp7iwbjdmxfk5-weechat-1.9.drv - aarch64-linux /var/log/guix/drvs/9y//p5dgijz8d09rm8v45lp7iwbjdmxfk5-weechat-1.9.drv.bz2
grafting '/gnu/store/wxaahzim320znm1pkw75616z6bzii7i2-weechat-1.9' -> '/gnu/store/v47ink6v2bpv3szfs2jvcz51bgciram6-weechat-1.9'...
ERROR: In procedure variable-ref: Not a variable: (#f #t #t #t #t #t #t #t #t #t #f #t #t #t #t #f #f #t #t #t #t #t #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f
#f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f #f
#f #f)
builder for `/gnu/store/9yp5dgijz8d09rm8v45lp7iwbjdmxfk5-weechat-1.9.drv' failed with exit code 1


-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: 'core-updates' status

[Marius Bakke]

[-- Attachment #1: Type: text/plain, Size: 508 bytes --]

Marius Bakke <mbakke@fastmail.com> writes:

> What do you think, are we ready to merge this branch?  There are ~2k
> armhf packages left in the queue, but many of them have already changed
> in 'master' and thus will need to be rebuilt anyway.

I started a (hopefully final) evaluation while waiting for a consensus.

Please try to `guix pull --branch=core-updates` and check that things
are working fine on your end.  Let's merge this as soon as x86_64 and
i686 is built out in lieu of any new regressions.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

Re: 'core-updates' status

[Marius Bakke]

[-- Attachment #1: Type: text/plain, Size: 720 bytes --]

Marius Bakke <mbakke@fastmail.com> writes:

> Marius Bakke <mbakke@fastmail.com> writes:
>
>> What do you think, are we ready to merge this branch?  There are ~2k
>> armhf packages left in the queue, but many of them have already changed
>> in 'master' and thus will need to be rebuilt anyway.
>
> I started a (hopefully final) evaluation while waiting for a consensus.
>
> Please try to `guix pull --branch=core-updates` and check that things
> are working fine on your end.  Let's merge this as soon as x86_64 and
> i686 is built out in lieu of any new regressions.

Hello!

'core-updates' has finished building on x86_64 on i686, and the grafting
failures should now be fixed.  Are we ready to merge this branch? :-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

Re: 'core-updates' status

[Leo Famulari]

[-- Attachment #1: Type: text/plain, Size: 342 bytes --]

On Fri, Aug 25, 2017 at 08:34:21PM +0200, Marius Bakke wrote:
> 'core-updates' has finished building on x86_64 on i686, and the grafting
> failures should now be fixed.  Are we ready to merge this branch? :-)

I think it's ready. There are a handful of failing packages left, but I
assume they will be fixed by their users after the merge :)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: 'core-updates' status

[Ludovic Courtès]

Leo Famulari <leo@famulari.name> skribis:

> On Fri, Aug 25, 2017 at 08:34:21PM +0200, Marius Bakke wrote:
>> 'core-updates' has finished building on x86_64 on i686, and the grafting
>> failures should now be fixed.  Are we ready to merge this branch? :-)
>
> I think it's ready. There are a handful of failing packages left, but I
> assume they will be fixed by their users after the merge :)

Seconded!  I upgraded my whole profile a couple of days ago, and I’m
still alive.  :-)

I’ll look at the cross-compilation issue, but it’s too late to realize
there’s a problem in this area I’m afraid.

Ludo’.

Re: 'core-updates' status

[Manolis Ragkousis]

On 08/26/2017 03:04 PM, Ludovic Courtès wrote:
> Leo Famulari <leo@famulari.name> skribis:
> 
>> On Fri, Aug 25, 2017 at 08:34:21PM +0200, Marius Bakke wrote:
>>> 'core-updates' has finished building on x86_64 on i686, and the grafting
>>> failures should now be fixed.  Are we ready to merge this branch? :-)
>>
>> I think it's ready. There are a handful of failing packages left, but I
>> assume they will be fixed by their users after the merge :)
> 
> Seconded!  I upgraded my whole profile a couple of days ago, and I’m
> still alive.  :-)
> 
> I’ll look at the cross-compilation issue, but it’s too late to realize
> there’s a problem in this area I’m afraid.
> 
> Ludo’.
> 

It's broken both in master and core-updates, so it must be a while this
problem went unnoticed . I will file a bug report per Leo's suggestion.
I am currently trying to find when/where did it break.

Thank you,
Manolis

core-updates merged!

[Marius Bakke]

[-- Attachment #1: Type: text/plain, Size: 676 bytes --]

Ludovic Courtès <ludo@gnu.org> writes:

> Leo Famulari <leo@famulari.name> skribis:
>
>> On Fri, Aug 25, 2017 at 08:34:21PM +0200, Marius Bakke wrote:
>>> 'core-updates' has finished building on x86_64 on i686, and the grafting
>>> failures should now be fixed.  Are we ready to merge this branch? :-)
>>
>> I think it's ready. There are a handful of failing packages left, but I
>> assume they will be fixed by their users after the merge :)
>
> Seconded!  I upgraded my whole profile a couple of days ago, and I’m
> still alive.  :-)

I went ahead and merged it.  Hope you have good bandwidth at the GHM!

\o/

(Also, see you guys there next year ;-))

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

Re: core-updates merged!

[Ludovic Courtès]

Howdy!

Marius Bakke <mbakke@fastmail.com> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Leo Famulari <leo@famulari.name> skribis:
>>
>>> On Fri, Aug 25, 2017 at 08:34:21PM +0200, Marius Bakke wrote:
>>>> 'core-updates' has finished building on x86_64 on i686, and the grafting
>>>> failures should now be fixed.  Are we ready to merge this branch? :-)
>>>
>>> I think it's ready. There are a handful of failing packages left, but I
>>> assume they will be fixed by their users after the merge :)
>>
>> Seconded!  I upgraded my whole profile a couple of days ago, and I’m
>> still alive.  :-)
>
> I went ahead and merged it.  Hope you have good bandwidth at the GHM!

Actually bandwidth was not good… but the meeting was great.  :-)

Super happy we merged before summer was over, so kudos to you and Leo
and everyone who cajoled the branch!

Who wants to volunteer as a time keeper for the next cycle?  The task of
the time keeper is to make sure we merge on time, which means saying
“no” when someone wants to push one of those infamous last-minute
rebuild-the-world changes, and pinging people regularly when we’re in
the phase where we’re fixing packages.  Any takers?

Ludo’.

PS: Cross-compilation isn’t entirely broken AFAICS:

--8<---------------cut here---------------start------------->8---
$ ./pre-inst-env guix build coreutils --target=arm-linux-gnueabihf -n
107.4 MB would be downloaded:
   /gnu/store/qz9v234ibskh09mcrmxjdy6x9bv4zyd0-binutils-cross-arm-linux-gnueabihf-2.28
   /gnu/store/lxs1nmi1a5kp7lz3hk8y2152ipwwpnva-gmp-6.1.2
   /gnu/store/j2nrcggkcxfbggd56bd4nzpaljr87mwv-gcc-cross-arm-linux-gnueabihf-5.4.0
   /gnu/store/z74c0dfgy7vpi0lg9axaz7x40sv9yk9r-glibc-cross-arm-linux-gnueabihf-2.25
   /gnu/store/dbzs50qvfnrddshr0nlxddk0cxd3rlh0-acl-2.2.52
   /gnu/store/wb4kd860x4ql181n073hzswcqb7l8qha-gcc-cross-sans-libc-arm-linux-gnueabihf-5.4.0
   /gnu/store/2dk2zk17allsh1j0hawxwpp47j1db5c5-attr-2.4.47
--8<---------------cut here---------------end--------------->8---

Re: 'core-updates' status

[Manolis Ragkousis]

On 08/25/17 21:34, Marius Bakke wrote:
> Hello!
> 
> 'core-updates' has finished building on x86_64 on i686, and the grafting
> failures should now be fixed.  Are we ready to merge this branch? :-)
> 

Does cross-compilation work? Because I cannot cross-compile anything for
any target I tried (i686-linux, i586-gnu).

http://paste.lisp.org/display/354303

Manolis

Re: 'core-updates' status

[Leo Famulari]

[-- Attachment #1: Type: text/plain, Size: 608 bytes --]

On Fri, Aug 25, 2017 at 10:57:12PM +0300, Manolis Ragkousis wrote:
> On 08/25/17 21:34, Marius Bakke wrote:
> > Hello!
> > 
> > 'core-updates' has finished building on x86_64 on i686, and the grafting
> > failures should now be fixed.  Are we ready to merge this branch? :-)
> > 
> 
> Does cross-compilation work? Because I cannot cross-compile anything for
> any target I tried (i686-linux, i586-gnu).
> 
> http://paste.lisp.org/display/354303

Can you file a bug report? Do you know if this is a new regression or
has it been present for the last couple months of core-updates
development?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]