zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: "Jun. T" <takimoto-j@kba.biglobe.ne.jp>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: [PATCH] Tests for 50126, 50136, and 50149
Date: Mon, 2 May 2022 09:26:28 -0700	[thread overview]
Message-ID: <CAH+w=7Zf4rXgV3D-7yS=Wu=khdN=SAxDdPOTmxFYnuKUDCK7XQ@mail.gmail.com> (raw)
In-Reply-To: <0A413565-C566-4A4A-8C67-C5F4E7C0A6A4@kba.biglobe.ne.jp>

On Mon, May 2, 2022 at 6:15 AM Jun. T <takimoto-j@kba.biglobe.ne.jp> wrote:
>
> I tested on a few other Macs.
> The test fails only on Monterey (12), either Apple M1 or Intel.
> It passes on Mojave (10.14), Catalina (10.15) and Big Sur (11).

OK, it's probably a process-switching thing then.  The sleep might fix
it by assuring that the background multio job can flush its output
before the test job tries to read it.  Could try writing directly to
temp files from the multio instead of using stdout and stderr, but
since those are directed to files anyway I'm not sure it would matter.


      reply	other threads:[~2022-05-02 16:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-30 18:31 A second test release before 5.9 final? Bart Schaefer
2022-04-30 21:41 ` dana
2022-05-01 14:52 ` Daniel Shahaf
2022-05-01 16:50   ` Bart Schaefer
2022-05-01 17:38     ` Daniel Shahaf
2022-05-02  2:24       ` Jun T
2022-05-02  3:10         ` Bart Schaefer
2022-05-02  4:09           ` Jun T
2022-05-02 12:58           ` Daniel Shahaf
2022-05-01 17:49     ` Peter Stephenson
2022-05-01 18:09     ` [PATCH] Test for 50101 Bart Schaefer
2022-05-01 19:09     ` [PATCH] Tests for 50126, 50136, and 50149 Bart Schaefer
2022-05-02  4:59       ` Jun T
2022-05-02  5:15         ` Bart Schaefer
2022-05-02  5:46           ` Jun T
2022-05-02 13:14         ` Jun. T
2022-05-02 16:26           ` Bart Schaefer [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='CAH+w=7Zf4rXgV3D-7yS=Wu=khdN=SAxDdPOTmxFYnuKUDCK7XQ@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=takimoto-j@kba.biglobe.ne.jp \
    --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).