Let’s fix build failures on ‘staging’!

Let’s fix build failures on ‘staging’!

[Ludovic Courtès]

Hello Guix!

Looking at
<https://hydra.gnu.org/eval/109427?compare=master#tabs-now-fail> we have
a few new failures:

  • Ardour fails its ‘configure’ phase
    https://hydra.gnu.org/build/1749839

  • there’s 1 tests failure in python2-pygpgme (breaks many things)
    https://hydra.gnu.org/build/1752661

  • kcrash fails to run its test with Xvfb (breaks all of KDE)
    https://hydra.gnu.org/build/1750201

  • NSS test failure on ARM (breaks many things)
    https://hydra.gnu.org/build/1749670

  • python2-pillow test failures on ARM
    https://hydra.gnu.org/build/1751907

  • ENOSPC on mips64el
    https://hydra.gnu.org/build/1742430

Let’s fix those!

Ludo’.

Re: Let’s fix build failures on ‘staging’!

[Leo Famulari]

On Sat, Jan 07, 2017 at 12:50:33PM +0100, Ludovic Courtès wrote:
>   • python2-pillow test failures on ARM
>     https://hydra.gnu.org/build/1751907

All these failures appear to be something timing out, like this:

nose.plugins.multiprocess.TimedOutException: 'TestFileJpeg.test_subsampling'

So I just restarted it.

Re: Let’s fix build failures on ‘staging’!

[Leo Famulari]

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

On Sat, Jan 07, 2017 at 12:50:33PM +0100, Ludovic Courtès wrote:
>   • NSS test failure on ARM (breaks many things)
>     https://hydra.gnu.org/build/1749670

I'm not sure about this. How about we revert the update on staging and
create an nss-updates branch with the latest release, 3.28.1?

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

Re: Let’s fix build failures on ‘staging’!

[Ludovic Courtès]

Leo Famulari <leo@famulari.name> skribis:

> On Sat, Jan 07, 2017 at 12:50:33PM +0100, Ludovic Courtès wrote:
>>   • NSS test failure on ARM (breaks many things)
>>     https://hydra.gnu.org/build/1749670
>
> I'm not sure about this. How about we revert the update on staging and
> create an nss-updates branch with the latest release, 3.28.1?

Yes it would probably be safer, unless the previous version has security
issues of course.

Ludo’.

Re: Let’s fix build failures on ‘staging’!

[Leo Famulari]

On Sat, Jan 07, 2017 at 10:32:59PM +0100, Ludovic Courtès wrote:
> Leo Famulari <leo@famulari.name> skribis:
> 
> > On Sat, Jan 07, 2017 at 12:50:33PM +0100, Ludovic Courtès wrote:
> >>   • NSS test failure on ARM (breaks many things)
> >>     https://hydra.gnu.org/build/1749670
> >
> > I'm not sure about this. How about we revert the update on staging and
> > create an nss-updates branch with the latest release, 3.28.1?
> 
> Yes it would probably be safer, unless the previous version has security
> issues of course.

None that I know of. In any case, we should work on merging this staging
branch, and I'll create the nss-updates branch later tonight.

Re: Let’s fix build failures on ‘staging’!

[Leo Famulari]

On Sat, Jan 07, 2017 at 12:50:33PM +0100, Ludovic Courtès wrote:
> Hello Guix!
> 
> Looking at
> <https://hydra.gnu.org/eval/109427?compare=master#tabs-now-fail> we have
> a few new failures:

I just started a new evaluation.

Status of ‘staging’ branch?

[Ludovic Courtès]

Hello Guix!

Apparently ‘staging’ is fully built on i686/x86_64.  Should we merge it?

I’d like to start building ‘core-updates’ now (we’re 6 days late :-)),
but we should get ‘staging’ out of the way first.

Thanks,
Ludo’.

Re: Status of ‘staging’ branch?

[Marius Bakke]

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

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

> Hello Guix!
>
> Apparently ‘staging’ is fully built on i686/x86_64.  Should we merge it?
>
> I’d like to start building ‘core-updates’ now (we’re 6 days late :-)),
> but we should get ‘staging’ out of the way first.

I think we can start building the 'core' package set now, no? Does it
include dbus/glib?

There are a quite a few ruby packages failing after the switch to 2.4:

https://hydra.gnu.org/eval/109665?compare=master#tabs-now-fail

We also have test failures in "lightdm" and "sssd":

https://hydra.gnu.org/build/2084542
https://hydra.gnu.org/build/2085014

(I can't reproduce the grub failure - luckily ;-))

I'm okay with merging now and dealing with the rest on 'master', but
would suggest trying to fix (some of) them first while we wait for the
'core' evaluation on Hydra. WDYT?

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

Re: Status of ‘staging’ branch?

[Marius Bakke]

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

Marius Bakke <mbakke@fastmail.com> writes:

> There are a quite a few ruby packages failing after the switch to 2.4:
>
> https://hydra.gnu.org/eval/109665?compare=master#tabs-now-fail
>
> We also have test failures in "lightdm" and "sssd":
>
> https://hydra.gnu.org/build/2084542
> https://hydra.gnu.org/build/2085014
>
> (I can't reproduce the grub failure - luckily ;-))

Actually, I can't reproduce the sssd failure either.

So, we have a bunch of failing ruby libraries, and lightdm (which
doesn't yet have a service, so should not break any system
configurations).

I will try to sort out some of the ruby stuff this weekend, but feel
free to merge it earlier!

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

Let’s fix build failures on ‘staging’!

[Ludovic Courtès]

Marius Bakke <mbakke@fastmail.com> skribis:

> Marius Bakke <mbakke@fastmail.com> writes:
>
>> There are a quite a few ruby packages failing after the switch to 2.4:
>>
>> https://hydra.gnu.org/eval/109665?compare=master#tabs-now-fail
>>
>> We also have test failures in "lightdm" and "sssd":
>>
>> https://hydra.gnu.org/build/2084542
>> https://hydra.gnu.org/build/2085014
>>
>> (I can't reproduce the grub failure - luckily ;-))
>
> Actually, I can't reproduce the sssd failure either.
>
> So, we have a bunch of failing ruby libraries, and lightdm (which
> doesn't yet have a service, so should not break any system
> configurations).
>
> I will try to sort out some of the ruby stuff this weekend, but feel
> free to merge it earlier!

I’d say let’s give people a couple of days to fix more problems, and
then merge!

Thanks,
Ludo’.