proot: Build gets stuck in test-0cf405b0 (and maybe test-25069c13)

Hi! It looks like some tests during the build of `proot` get stuck in the

version of Guix shown below:

```

$ LANG=C guix describe

Generation 56 May 02 2023 11:25:26 (current)

guix 3f8c489

repository URL: https://git.savannah.gnu.org/git/guix.git

branch: master

commit: 3f8c4899a9a67bb509a603bd21dcfcfab88c0e8e

```

Since `top` reported a couple of tests getting stuck, I first ran `guix build

-c1 proot`; its last lines were:

```

CHECK test-pppppppp ok

CHECK test-proocare skipped

CHECK test-ptrace-exec-trap ok

CHECK test-python01 ok

CHECK test-rrrrrrrr ok

CHECK test-tempdire ok

CHECK test-wwwwwwww ok

CHECK test-yyyyyyyy ok

```

It got stock there and `top` reported the following test (`test-0cf405b0`)

using CPU:

```

21490 guixbui+ 20 0 10,8m 4,0m 0,0 0,0 0:00.03 S `- make check -C test -j 1

24340 guixbui+ 20 0 6,4m 2,9m 0,0 0,0 0:00.00 S `- /gnu/store/rib9g2ig1xf3kclyl076w28parmncg4k-bash-minimal-5.1.16/bin/sh -c if [ -e /tmp/guix-build-proot-5.3.0.drv-0/source/test//rootfs/bin/test-0cf405b0 ]; then /tmp/guix+

24341 guixbui+ 20 0 7,1m 3,1m 55,0 0,0 0:42.21 S `- /tmp/guix-build-proot-5.3.0.drv-0/source/test//../src/proot -b /proc -r /tmp/guix-build-proot-5.3.0.drv-0/source/test//rootfs /bin/test-0cf405b0

24342 guixbui+ 20 0 0,9m 0,4m 45,7 0,0 0:34.71 t `-

```

Then I ran again `guix build -c4 proot` (4 cores is the default on my

computer); its last lines were:

```

CHECK test-pppppppp ok

CHECK test-proocare skipped

CHECK test-ptrace-exec-trap ok

CHECK test-python01 ok

CHECK test-rrrrrrrr ok

CHECK test-tempdire ok

CHECK test-wwwwwwww ok

CHECK test-yyyyyyyy ok

CHECK test-gdb-ptrace ok

CHECK test-1c68c218 ok

CHECK test-305ae31d ok

CHECK test-33333333 ok

CHECK test-33333334 ok

CHECK test-44444444 ok

CHECK test-51943658 ok

CHECK test-66666666 ok

CHECK test-79cf6614 ok

CHECK test-88888888 ok

CHECK test-a8e69d6f ok

CHECK test-af062114 ok

CHECK test-bug-138 ok

CHECK test-c10e2073 ok

CHECK test-d2175fc4 ok

CHECK test-e87b34ae ok

CHECK test-nnnnnnnn ok

CHECK test-oooooooo ok

CHECK test-ptrace00 ok

CHECK test-ptrace01 ok

CHECK test-ssssssss ok

CHECK test-xxxxxxxx ok

```

It got stock there and `top` reported the following tests (`test-0cf405b0` and

`test-25069c12`) taking CPU:

```

9960 guixbui+ 20 0 11,0m 4,0m 0,0 0,0 0:00.06 S `- make check -C test -j 4

10535 guixbui+ 20 0 6,4m 2,9m 0,0 0,0 0:00.00 S `- /gnu/store/rib9g2ig1xf3kclyl076w28parmncg4k-bash-minimal-5.1.16/bin/sh -c if [ -e test-25069c12 ]; then /tmp/guix-build-proot-5.3.0.drv-0/source/test//../src/proot ./test-+

10536 guixbui+ 20 0 7,1m 3,1m 66,0 0,0 17:29.84 R `- /tmp/guix-build-proot-5.3.0.drv-0/source/test//../src/proot ./test-25069c12

10537 guixbui+ 20 0 0,4m 0,1m 32,1 0,0 8:36.58 t `-

10543 guixbui+ 20 0 6,4m 2,9m 0,0 0,0 0:00.00 S `- /gnu/store/rib9g2ig1xf3kclyl076w28parmncg4k-bash-minimal-5.1.16/bin/sh -c if [ -e test-25069c13 ]; then /tmp/guix-build-proot-5.3.0.drv-0/source/test//../src/proot ./test-+

10544 guixbui+ 20 0 7,1m 3,1m 66,0 0,0 17:29.99 R `- /tmp/guix-build-proot-5.3.0.drv-0/source/test//../src/proot ./test-25069c13

10545 guixbui+ 20 0 0,4m 0,1m 32,1 0,0 8:36.61 t `-

13202 guixbui+ 20 0 6,4m 2,9m 0,0 0,0 0:00.00 S `- /gnu/store/rib9g2ig1xf3kclyl076w28parmncg4k-bash-minimal-5.1.16/bin/sh -c if [ -e /tmp/guix-build-proot-5.3.0.drv-0/source/test//rootfs/bin/test-0cf405b0 ]; then /tmp/guix+

13203 guixbui+ 20 0 7,1m 3,1m 52,8 0,0 13:52.96 S `- /tmp/guix-build-proot-5.3.0.drv-0/source/test//../src/proot -b /proc -r /tmp/guix-build-proot-5.3.0.drv-0/source/test//rootfs /bin/test-0cf405b0

13204 guixbui+ 20 0 0,9m 0,0m 44,0 0,0 11:43.34 R `-

```

Thanks and cheers!

--

Ivan Vilata i Balaguer -- https://elvil.net/

Hi Ivan,

Ivan Vilata i Balaguer <ivan@selidor.net> writes:

I already provided fixes for two tests upstream [1] but I'm waiting on

[2] since it seems like an actual regression.

[1] https://github.com/proot-me/proot/pull/351

[2] https://github.com/proot-me/proot/issues/352

Best,

--

Josselin Poiret

I'm also dealing with the issue, except for me it gets stuck in

test-kkkkkkk, if that info is helpful at all.

Josselin Poiret via Bug reports for GNU Guix <bug-guix@gnu.org> writes:

merge 63394 63284

thankyou

Hi André,

André A. Gomes <andremegafone@gmail.com> writes:

See [1] for more information. One of the tests failing is actually

indicative of a regression in proot I think, so this is why we haven't

gotten around to fixing it yet.

[1] https://issues.guix.gnu.org/63284

Best,

--

Josselin Poiret

Same for me both building with:

guix build proot --with-version=proot=5.4.0

And altering the definition of the package manually to use `(version "5.4.0")`

(hash `186qsg4yvisqjgf8w5jxhnlig7x341vpqwcgp8as3r59qmqkpmk7`), plus removing

`libarchive` from `inputs` (as v5.3.1 already removed that dependency).

Thanks!

Blake Shaw (2023-05-07 15:55:04 +0700) wrote:

--

Ivan Vilata i Balaguer -- https://elvil.net/

merge 63843 63394

close 63394

thankyou

Hi Ontje,

<Ontje.Luensdorf@dlr.de> writes:

This is fixed by b741218e919bfd386772322c1dcb286446bc4c90. Note that

disabling the tests here was a bad idea, as the upstream issue

indicated: this was a regression.

Best,

--

Josselin Poiret