bug#41661: [Cuirass] Doesn't honor 'timeout' nor 'max-silent-time' leading to mising substitutes

bug#41661: [Cuirass] Doesn't honor 'timeout' nor 'max-silent-time' leading to mising substitutes

[Brice Waegeneire]

Hello Guix,

Unlike Hydra, Curiass don't honor 'timeout' and 'max-silent-time'
properties[0]. This lead to some packages never having substitutes, in
particular for the 'armhf-linux' system for example 'linux-libre' or
'guile-static-stripped'[1]. Which mean it's really difficult to use such
systems since each users need to build thoses really long running[2]
packages. We also don't know if thoses package may fail for a reason 
other
than timing out.

[0]: https://lists.gnu.org/archive/html/guix-devel/2020-03/msg00209.html
[1]: 
http://ci.guix.gnu.org/search?query=guile-static-stripped%20system:armhf-linux
[2]: 
https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/guile.scm?id=f51fd97ec54a98668d63c52d8a6bd75d8dc3292e#n257

- Brice

bug#41661: [Cuirass] Doesn't honor 'timeout' nor 'max-silent-time' leading to mising substitutes

[Leo Famulari]

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

On Tue, Jun 02, 2020 at 01:15:19PM +0000, Brice Waegeneire wrote:
> Hello Guix,
> 
> Unlike Hydra, Curiass don't honor 'timeout' and 'max-silent-time'
> properties[0]. This lead to some packages never having substitutes, in
> particular for the 'armhf-linux' system for example 'linux-libre' or
> 'guile-static-stripped'[1]. Which mean it's really difficult to use such
> systems since each users need to build thoses really long running[2]
> packages. We also don't know if thoses package may fail for a reason other
> than timing out.
> 
> [0]: https://lists.gnu.org/archive/html/guix-devel/2020-03/msg00209.html
> [1]: http://ci.guix.gnu.org/search?query=guile-static-stripped%20system:armhf-linux
> [2]: https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/guile.scm?id=f51fd97ec54a98668d63c52d8a6bd75d8dc3292e#n257
> 
> - Brice

We really need to improve our CI so that it's possible to discover these
build failures. Currently it's quite hard to monitor if they get built
unless you just do `guix build foo`.

The last time this came up [0] it was said that maybe it's not really
correct to make these properties of the package, but rather of the CI
jobs. It makes sense but we need a solution, or stop supporting
underpowered architectures like armhf, because most of those machines
can't build this stuff themselves, and it's not good to advertise
support to people who will just be disappointed later.

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

bug#41661: [Cuirass] Doesn't honor 'timeout' nor 'max-silent-time' leading to mising substitutes

[Ludovic Courtès]

Hi,

Leo Famulari <leo@famulari.name> skribis:

> We really need to improve our CI so that it's possible to discover these
> build failures. Currently it's quite hard to monitor if they get built
> unless you just do `guix build foo`.

Or ‘guix weather’, which is not worse than a web UI IMO.

> The last time this came up [0] it was said that maybe it's not really
> correct to make these properties of the package, but rather of the CI
> jobs. It makes sense but we need a solution, or stop supporting
> underpowered architectures like armhf, because most of those machines
> can't build this stuff themselves, and it's not good to advertise
> support to people who will just be disappointed later.

Yeah.  I think we need to look at these on a case-by-case basis.  Guile
is one of those packages known to hit the max-silent-time of 1h (?)
that’s configured on berlin.  Hopefully it will no longer be the case
starting from 3.0.3.

What about Linux-libre?  Does it hit the max absolute build time on
armhf?

As I wrote elsewhere, I think it makes more sense in a way to have
those timeouts configured system-wide.  But yeah, we need to be
pragmatic.

Thanks,
Ludo’.

bug#41661: [Cuirass] Doesn't honor 'timeout' nor 'max-silent-time' leading to mising substitutes

[Brice Waegeneire]

Hello,

On 2020-06-04 12:16, Ludovic Courtès wrote:
> Hi,
> 
> Leo Famulari <leo@famulari.name> skribis:
> 
>> We really need to improve our CI so that it's possible to discover 
>> these
>> build failures. Currently it's quite hard to monitor if they get built
>> unless you just do `guix build foo`.
> 
> Or ‘guix weather’, which is not worse than a web UI IMO.

+1 for CLI tools!

>> The last time this came up [0] it was said that maybe it's not really
>> correct to make these properties of the package, but rather of the CI
>> jobs. It makes sense but we need a solution, or stop supporting
>> underpowered architectures like armhf, because most of those machines
>> can't build this stuff themselves, and it's not good to advertise
>> support to people who will just be disappointed later.
> 
> Yeah.  I think we need to look at these on a case-by-case basis.  Guile
> is one of those packages known to hit the max-silent-time of 1h (?)
> that’s configured on berlin.  Hopefully it will no longer be the case
> starting from 3.0.3.
> 
> What about Linux-libre?  Does it hit the max absolute build time on
> armhf?

I misdiagnosed the issue, substitutes for it are available now and 
previous
seems to be there too.  IDK why it wasn't available before nor why I
couldn't manage to built it myself.

> As I wrote elsewhere, I think it makes more sense in a way to have
> those timeouts configured system-wide.  But yeah, we need to be
> pragmatic.
> 
> Thanks,
> Ludo’.

- Brice

bug#41661: [Cuirass] Doesn't honor 'timeout' nor 'max-silent-time' leading to mising substitutes

[Mathieu Othacehe]

Hello,

Cuirass now honors those properties, closing this one.

Thanks,

Mathieu