proot-static build failures (master and core-updates)

proot-static build failures (master and core-updates)

[Greg Hogan]

We now have a build attempt on Cuirass:
https://ci.guix.gnu.org/build/982993/details

proot-static is required for building relocatable packages.

That is on core-updates, but I see the same issue building from source
on master, as well as running manually outside of the proot. The check
fails on timeout, but test-25069c12 and test-25069c13 are trivial and
I can see no reason why these test processes do not terminate
immediately rather than execve continually.

Greg

Re: proot-static build failures (master and core-updates)

[Ludovic Courtès]

Hi,

Greg Hogan <code@greghogan.com> skribis:

> We now have a build attempt on Cuirass:
> https://ci.guix.gnu.org/build/982993/details
>
> proot-static is required for building relocatable packages.

Yup, so that’s a problem.

> That is on core-updates, but I see the same issue building from source
> on master, as well as running manually outside of the proot. The check
> fails on timeout, but test-25069c12 and test-25069c13 are trivial and
> I can see no reason why these test processes do not terminate
> immediately rather than execve continually.

Josselin mentioned on IRC that they’d reported it upstream:

  https://github.com/proot-me/proot/issues/352

Do these tests reveal a real issue, or should we just skip them until a
fix lands upstream?

Ludo’.

Re: proot-static build failures (master and core-updates)

[Josselin Poiret]

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

Hi Ludo,

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

> Josselin mentioned on IRC that they’d reported it upstream:
>
>   https://github.com/proot-me/proot/issues/352
>
> Do these tests reveal a real issue, or should we just skip them until a
> fix lands upstream?

From what I understand of the failing test it looks like an actual
regression.

Best,
-- 
Josselin Poiret

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