unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Ivan Vilata i Balaguer <ivan@selidor.net>
To: 63284@debbugs.gnu.org
Subject: bug#63284: proot: Build gets stuck in test-0cf405b0 (and maybe test-25069c13)
Date: Thu, 4 May 2023 23:52:32 +0200	[thread overview]
Message-ID: <ZFQpIBtacbPKNJ60@sax> (raw)

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

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/

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

             reply	other threads:[~2023-05-04 21:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-04 21:52 Ivan Vilata i Balaguer [this message]
2023-05-05  9:31 ` bug#63284: proot: Build gets stuck in test-0cf405b0 (and maybe test-25069c13) Josselin Poiret via Bug reports for GNU Guix
2023-05-07  8:55   ` Blake Shaw via Bug reports for GNU Guix
2023-05-19 12:36     ` Ivan Vilata i Balaguer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZFQpIBtacbPKNJ60@sax \
    --to=ivan@selidor.net \
    --cc=63284@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).