From: "Ludovic Courtès" <ludo@gnu.org>
To: Z572 <873216071@qq.com>
Cc: 63675@debbugs.gnu.org, Efraim Flashner <efraim@flashner.co.il>
Subject: bug#63675: shepherd 0.10.0 test 2 fail on riscv64-linux
Date: Thu, 25 May 2023 16:53:42 +0200 [thread overview]
Message-ID: <87zg5scvih.fsf@gnu.org> (raw)
In-Reply-To: <tencent_D652EDB2E6FF9275F2CA1B4B4E6AFF366509@qq.com> (873216071@qq.com's message of "Wed, 24 May 2023 11:43:12 +0800")
Hi,
(Cc: Efraim as another RISC-V person.)
Z572 <873216071@qq.com> skribis:
> shepherd 0.10.0 test 2 fail on riscv64-linux. same error use
> `guix build shepherd -s riscv64-linux` on x86_64 or
> `guix build shepherd` on riscv64.
[…]
> FAIL: tests/forking-service
[…]
> + herd -s t-socket-3968 start test
> Starting service test...
> Service test has been started.
> + herd -s t-socket-3968 start test2
> Starting service test2...
> Service test2 has been started.
> + grep running
> + herd -s t-socket-3968 status test
> It is running since 03:39:18 (3 seconds ago).
> + test -f t-service-pid-3968
> ++ cat t-service-pid-3968
> + service_pid_value=6499
> + kill 6499
> + kill -0 6499
> + sleep 0.3
> + kill -0 6499
> + sleep 0.3
> + kill -0 6499
Here it looks as though process 6499 (associated with service ‘test’) is
either not receiving SIGHUP as sent by “kill 6499” or is ignoring it.
How reproducible is it? You can run it with
“make check TESTS=tests/forking-service.sh” to see.
Thanks,
Ludo’.
next prev parent reply other threads:[~2023-05-25 15:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 3:43 bug#63675: shepherd 0.10.0 test 2 fail on riscv64-linux Z572 via Bug reports for GNU Guix
2023-05-24 3:43 ` Z572 via Bug reports for GNU Guix
2023-05-25 14:53 ` Ludovic Courtès [this message]
2023-05-25 14:59 ` Ludovic Courtès
2023-06-11 14:15 ` Z572 via Bug reports for GNU Guix
2023-06-11 14:15 ` Z572 via Bug reports for GNU Guix
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=87zg5scvih.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=63675@debbugs.gnu.org \
--cc=873216071@qq.com \
--cc=efraim@flashner.co.il \
/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.