From: "Ludovic Courtès" <ludo@gnu.org>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 45791@debbugs.gnu.org
Subject: bug#45791: guix publish test never completes.
Date: Thu, 21 Jan 2021 13:58:25 +0100 [thread overview]
Message-ID: <87sg6ua1la.fsf@inria.fr> (raw)
In-Reply-To: <87zh1f4gt5.fsf@gnu.org>
Hi,
Mathieu Othacehe <othacehe@gnu.org> skribis:
> 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:
--8<---------------cut here---------------start------------->8---
[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)
--8<---------------cut here---------------end--------------->8---
… 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’.
prev parent reply other threads:[~2021-01-21 13:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 15:46 bug#45791: guix publish test never completes Mathieu Othacehe
2021-01-21 12:58 ` Ludovic Courtès [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sg6ua1la.fsf@inria.fr \
--to=ludo@gnu.org \
--cc=45791@debbugs.gnu.org \
--cc=othacehe@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.