From: Jeff King <peff@peff.net>
To: "brian m. carlson" <sandals@crustytoothpaste.net>,
Lars Schneider <larsxschneider@gmail.com>,
Junio C Hamano <gitster@pobox.com>, Mike Hommey <mh@glandium.org>,
git@vger.kernel.org
Subject: Re: [PATCH] travis-ci: run previously failed tests first, then slowest to fastest
Date: Fri, 22 Jan 2016 00:52:55 -0500 [thread overview]
Message-ID: <20160122055255.GA14657@sigill.intra.peff.net> (raw)
In-Reply-To: <20160122023359.GA686558@vauxhall.crustytoothpaste.net>
On Fri, Jan 22, 2016 at 02:33:59AM +0000, brian m. carlson wrote:
> > Especially t0025-crlf-auto.sh failed multiple times ([2], [3]) on the OS X builds
> > when I increase the parallelism:
> >
> > not ok 4 - text=true causes a CRLF file to be normalized
> > not ok 9 - text=auto, autocrlf=true _does_ normalize CRLF files
> >
> > Anyone an idea why that might be the case?
>
> I've seen this on my personal box too[0] when running make -j4 all test.
> I wasn't able to pin down why it was occurring, but if we're going to
> run the tests in parallel, it's probably worth spending some time
> figuring it out.
Interesting. I run the test suite in parallel probably a dozen times
per day, and I've never seen this. However, I was able to trigger it
eventually with:
for i in 1 2 3 4 5 6 7 8
do
(while ./t0025-crlf-auto.sh --root=/var/ram/git-tests/foo-$i -v -i >/tmp/foo-$i 2>&1
do
: nothing
done
echo FAILED $i
) &
done
I get a few of the threads failing (in test 4) after 2-3 minutes. The
"-v" output is pretty unenlightening, though. I don't see anything
racy-looking in the test unless it is something with "read-tree" and
stat mtimes.
-Peff
next prev parent reply other threads:[~2016-01-22 5:53 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 9:24 [PATCH] travis-ci: run previously failed tests first, then slowest to fastest larsxschneider
2016-01-19 19:12 ` Jeff King
2016-01-19 23:00 ` Junio C Hamano
2016-01-20 0:26 ` Mike Hommey
2016-01-20 1:46 ` Junio C Hamano
2016-01-20 1:56 ` Jeff King
2016-01-20 9:22 ` Lars Schneider
2016-01-22 2:33 ` brian m. carlson
2016-01-22 5:52 ` Jeff King [this message]
2016-01-22 6:07 ` Jeff King
2016-01-24 14:34 ` Thomas Gummerer
2016-01-24 20:03 ` Junio C Hamano
2016-01-24 22:05 ` Junio C Hamano
2016-01-25 14:42 ` Thomas Gummerer
2016-01-25 17:26 ` Junio C Hamano
2016-01-25 21:52 ` Junio C Hamano
2016-01-27 15:16 ` Clemens Buchacher
2016-01-27 19:05 ` Junio C Hamano
2016-01-27 20:49 ` Junio C Hamano
2016-01-28 7:10 ` Clemens Buchacher
2016-01-28 21:32 ` Junio C Hamano
2016-01-30 8:13 ` Clemens Buchacher
2016-02-01 18:17 ` Junio C Hamano
2016-02-01 19:33 ` Clemens Buchacher
2016-02-02 23:14 ` Junio C Hamano
2016-02-03 8:31 ` Junio C Hamano
2016-02-01 20:26 ` Torsten Bögershausen
2016-01-28 6:20 ` eol round trip Was: [PATCH] travis-ci: run previously failed Torsten Bögershausen
2016-01-25 22:41 ` [PATCH] travis-ci: run previously failed tests first, then slowest to fastest Thomas Gummerer
2016-01-20 1:53 ` Jeff King
2016-01-20 9:10 ` Lars Schneider
2016-01-19 20:00 ` Junio C Hamano
2016-01-19 22:53 ` Junio C Hamano
2016-01-19 23:06 ` Jeff King
2016-01-19 23:26 ` Junio C Hamano
2016-01-19 23:29 ` Jeff King
2016-01-19 23:30 ` Junio C Hamano
2016-01-19 23:27 ` Jeff King
2016-01-20 7:55 ` Johannes Schindelin
2016-01-20 9:04 ` Lars Schneider
2016-01-20 20:35 ` 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=20160122055255.GA14657@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=larsxschneider@gmail.com \
--cc=mh@glandium.org \
--cc=sandals@crustytoothpaste.net \
/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).