From: Andrej Shadura <andrew.shadura@collabora.co.uk>
To: dash@vger.kernel.org
Cc: Michael Biebl <biebl@debian.org>
Subject: Changes to job handling cause hangs in wait
Date: Mon, 16 Nov 2020 11:29:16 +0100 [thread overview]
Message-ID: <0b1af921-f0dc-33e1-eae3-91192c2ec60a@collabora.co.uk> (raw)
Hi,
I’d like to forward a bug report I received. Michael, who reported it,
was able to bisect it to 6c691b3, which was the first of the series of
commits changing job handling.
I must note that I had troubles debugging it: I was only able to
reproduce the issue in an autopkgtest virtual machine, but not on my
normal system nor in a fresh Debian unstable Docker container.
I’m considering reverting some of the relevant commits, but it’d be best
if we could track this down and get it fixed.
The full details can be found at: https://bugs.debian.org/974705
Thanks.
--
Cheers,
Andrej
next reply other threads:[~2020-11-16 11:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 10:29 Andrej Shadura [this message]
2020-11-17 3:33 ` Changes to job handling cause hangs in wait Herbert Xu
2020-12-01 5:38 ` Herbert Xu
2020-12-01 5:42 ` Herbert Xu
2020-12-01 6:06 ` Herbert Xu
2020-12-01 6:56 ` Herbert Xu
2020-12-01 23:21 ` Michael Biebl
2020-12-01 23:26 ` Herbert Xu
2020-12-02 5:31 ` [PATCH] jobs: Only block in waitcmd on first run Herbert Xu
2020-12-03 12:27 ` Changes to job handling cause hangs in wait Michael Biebl
2020-12-07 3:55 ` Herbert Xu
2020-12-03 12:49 ` Michael Biebl
2020-12-01 10:14 ` Harald van Dijk
2020-12-01 10:34 ` Herbert Xu
2020-12-01 10:50 ` Harald van Dijk
2020-12-01 10:53 ` Herbert Xu
2020-12-01 10:55 ` Harald van Dijk
2020-12-01 10:56 ` Herbert Xu
2020-12-01 10:59 ` Harald van Dijk
2020-12-01 11:01 ` Herbert Xu
2020-12-01 13:04 ` Michael Biebl
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=0b1af921-f0dc-33e1-eae3-91192c2ec60a@collabora.co.uk \
--to=andrew.shadura@collabora.co.uk \
--cc=biebl@debian.org \
--cc=dash@vger.kernel.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.
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 NNTP newsgroup(s).