From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Vin Shelton <acs@alumni.princeton.edu>
Cc: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: Test Failure. 2020-03-08
Date: Mon, 9 Mar 2020 01:59:55 +0000 [thread overview]
Message-ID: <20200309015955.1ca1d818@tarpaulin.shahaf.local2> (raw)
In-Reply-To: <CACeGjnVNtdeh2YAryXD6mLNkPYBmg=yuuXt=CUoY4zz7efT=Zg@mail.gmail.com>
Vin Shelton wrote on Sun, 08 Mar 2020 16:47 -0400:
> Sadly, nope:
>
> ZTST_verbose=2 make TESTNUM=V01 -e check
>
> yields the attached.
Thanks for the debug info. I've reproduced this now (didn't have time
for that yesterday) and pushed a fix to master. Sorry for the breakage.
Daniel
next prev parent reply other threads:[~2020-03-09 2:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-08 12:38 Vin Shelton
2020-03-08 15:27 ` Daniel Shahaf
2020-03-08 20:47 ` Vin Shelton
2020-03-09 1:59 ` Daniel Shahaf [this message]
2020-03-09 2:08 ` Vin Shelton
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=20200309015955.1ca1d818@tarpaulin.shahaf.local2 \
--to=d.s@daniel.shahaf.name \
--cc=acs@alumni.princeton.edu \
--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).