From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: Drat, Test/A05 still hanging sometimes
Date: Mon, 13 Oct 2014 10:18:03 -0700 [thread overview]
Message-ID: <141013101803.ZM5769@torch.brasslantern.com> (raw)
In-Reply-To: <20141013030313.GB5405@sym.noone.org>
On Oct 13, 5:03am, Axel Beckert wrote:
}
} On Sun, Oct 12, 2014 at 11:47:39AM -0700, Bart Schaefer wrote:
} > Tests in each of A01, A04, and A05 use "coproc". How does this match up
} > with the hung builds you have encountered?
}
} Quite well -- as far as I can see there was only one exception so far:
} Once it also hung inside X02zlevi.ztst. All others were either in one
} of the three tests you mentioned, with A05 being the most often one
} (and IIRC also the one you experience twice or so).
Give the following a try? With the "sleep" in there, I am unable to
make the A05 test hang. Without it, I get one hang in each 20 repeats
of the test, pretty reliably.
Although why putting the sleep at that particular place has the right
side-effect, I do not know.
diff --git a/Test/A05execution.ztst b/Test/A05execution.ztst
index ca97f4f..0b40a73 100644
--- a/Test/A05execution.ztst
+++ b/Test/A05execution.ztst
@@ -208,6 +208,7 @@ F:This similar test was triggering a reproducible failure with pipestatus.
print -u $ZTST_fd 'This test takes 5 seconds to fail...'
{ printf "%d\n" {1..20000} } | ( read -e )
hang(){ printf "%d\n" {2..20000} | cat }; hang | ( read -e )
+ sleep 1 ;: avoid coproc exit race condition
print -p done
read -et 6 -p
0:Bug regression: piping a shell construct to an external process may hang
next prev parent reply other threads:[~2014-10-13 17:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-06 20:42 Bart Schaefer
2014-10-07 14:07 ` Peter Stephenson
2014-10-09 7:52 ` Axel Beckert
2014-10-12 18:47 ` Bart Schaefer
2014-10-13 3:03 ` Axel Beckert
2014-10-13 17:18 ` Bart Schaefer [this message]
2014-10-14 9:34 ` Axel Beckert
2014-10-27 0:40 ` Bart Schaefer
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=141013101803.ZM5769@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@zsh.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.vuxu.org/mirror/zsh/
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).