guix publish test never completes.

  • Open
  • quality assurance status badge
Details
2 participants
  • Ludovic Courtès
  • Mathieu Othacehe
Owner
unassigned
Submitted by
Mathieu Othacehe
Severity
important

Debbugs page

M
M
Mathieu Othacehe wrote on 11 Jan 2021 07:46
(address . bug-guix@gnu.org)
87zh1f4gt5.fsf@gnu.org
Hello,

The "publish" test has been running for 28 hours on hydra-guix-126. The
matching process is:

Toggle snippet (3 lines)
guixbui+ 58019 109 0.2 4052284 465988 ? Rl Jan10 1718:33 /gnu/store/dxvxl29bb1kzqgb9bz8gfcyag177g9vj-guile-3.0.5/bin/guile --no-auto-compile -e main ./build-aux/test-driver.scm --test-name tests/publish.scm --log-file tests/publish.log --trs-file tests/publish.trs --color-tests no --enable-hard-errors yes --expect-failure no --brief=yes -- ./tests/publish.scm

An strace log of this process is attached. I would suspect "with cache,
cache bypass" test given that the looping connection is made on port
6788.

Thanks,

Mathieu
Attachment: strace_publish.txt.gz
L
L
Ludovic Courtès wrote on 13 Jan 2021 03:26
control message for bug #45791
(address . control@debbugs.gnu.org)
878s8xcc35.fsf@gnu.org
severity 45791 important
quit
L
L
Ludovic Courtès wrote on 21 Jan 2021 04:58
Re: bug#45791: guix publish test never completes.
(name . Mathieu Othacehe)(address . othacehe@gnu.org)(address . 45791@debbugs.gnu.org)
87sg6ua1la.fsf@inria.fr
Hi,

Mathieu Othacehe <othacehe@gnu.org> skribis:

Toggle quote (9 lines)
> The "publish" test has been running for 28 hours on hydra-guix-126. The
> matching process is:
>
> guixbui+ 58019 109 0.2 4052284 465988 ? Rl Jan10 1718:33 /gnu/store/dxvxl29bb1kzqgb9bz8gfcyag177g9vj-guile-3.0.5/bin/guile --no-auto-compile -e main ./build-aux/test-driver.scm --test-name tests/publish.scm --log-file tests/publish.log --trs-file tests/publish.trs --color-tests no --enable-hard-errors yes --expect-failure no --brief=yes -- ./tests/publish.scm
>
> An strace log of this process is attached. I would suspect "with cache,
> cache bypass" test given that the looping connection is made on port
> 6788.

The log shows an endless loop of:

Toggle snippet (3 lines)
[pid 58019] connect(853, {sa_family=AF_INET, sin_port=htons(6788), sin_addr=inet_addr("127.0.0.1")}, 16) = -1 ECONNREFUSED (Connection refused)

… which suggests nothing’s listening on port 6788, which probably means
that ‘guix publish’ didn’t start, for example due to EADDRINUSE (but the
log starts after that.)

Are you able to reproduce the issue with:

while make check TESTS=tests/publish.scm ; do : ; done

Surprisingly, port 6788 doesn’t seem to be used by any other test, which
probably rules out a problem due to concurrent tests using the same
port.

Also, was it the result of “guix build guix” or equivalent? In that
case tests run sequentially.

Thanks,
Ludo’.
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 45791@patchwise.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 45791
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch