From: Adam Dinwoodie <adam@dinwoodie.org>
To: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>,
Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: [ANNOUNCE] Git v2.27.0-rc0
Date: Tue, 19 May 2020 20:10:37 +0100 [thread overview]
Message-ID: <CA+kUOanbgUPgCer-sBjX6YROYvZAhzBTUtCnFvuYP1EWvo3VEA@mail.gmail.com> (raw)
In-Reply-To: <xmqqy2punll7.fsf@gitster.c.googlers.com>
On Fri, 15 May 2020 at 00:27, Junio C Hamano wrote:
>
> An early preview release Git v2.27.0-rc0 is now available for
> testing at the usual places. It is comprised of 479 non-merge
> commits since v2.26.0, contributed by 53 people, 16 of which are
> new faces.
>
> <snip>
>
> tests: when run in Bash, annotate test failures with file name/line number
At least on Cygwin, this breaks the test output parsing of failures
when running with prove.
Compare the expected behaviour, prior to this commit:
~~~
$ make -j17 && ( cd t && prove t4210-log-i18n.sh )
GIT_VERSION = 2.26.0.131.g6081d3898f
...
t4210-log-i18n.sh .. Dubious, test returned 1 (wstat 256, 0x100)
Failed 6/17 subtests
(less 3 skipped subtests: 8 okay)
Test Summary Report
-------------------
t4210-log-i18n.sh (Wstat: 256 Tests: 17 Failed: 6)
Failed tests: 6, 8-9, 11-12, 14
Non-zero exit status: 1
Files=1, Tests=17, 3 wallclock secs ( 0.05 usr 0.02 sys + 0.77 cusr
1.80 csys = 2.63 CPU)
Result: FAIL
~~~
with the new behaviour as of this commit:
~~~
$ make -j17 && ( cd t && prove t4210-log-i18n.sh )
GIT_VERSION = 2.26.0.132.g662f9cf154
...
t4210-log-i18n.sh .. Dubious, test returned 1 (wstat 256, 0x100)
Failed 6/17 subtests
(less 3 skipped subtests: 8 okay)
Test Summary Report
-------------------
t4210-log-i18n.sh (Wstat: 256 Tests: 11 Failed: 0)
Non-zero exit status: 1
Parse errors: Tests out of sequence. Found (7) but expected (6)
Tests out of sequence. Found (10) but expected (7)
Tests out of sequence. Found (13) but expected (8)
Tests out of sequence. Found (15) but expected (9)
Tests out of sequence. Found (16) but expected (10)
Displayed the first 5 of 7 TAP syntax errors.
Re-run prove with the -p option to see them all.
Files=1, Tests=11, 3 wallclock secs ( 0.02 usr 0.03 sys + 0.74 cusr
1.83 csys = 2.62 CPU)
Result: FAIL
~~~
next prev parent reply other threads:[~2020-05-19 19:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 23:27 [ANNOUNCE] Git v2.27.0-rc0 Junio C Hamano
2020-05-15 14:21 ` Randall S. Becker
2020-05-15 14:57 ` Junio C Hamano
2020-05-19 19:10 ` Adam Dinwoodie [this message]
2020-05-19 23:21 ` Junio C Hamano
2020-05-20 14:14 ` Adam Dinwoodie
2020-05-20 14:37 ` Junio C Hamano
2020-05-14 23:28 Junio C Hamano
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=CA+kUOanbgUPgCer-sBjX6YROYvZAhzBTUtCnFvuYP1EWvo3VEA@mail.gmail.com \
--to=adam@dinwoodie.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johannes.schindelin@gmx.de \
/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).