From: Derrick Stolee <stolee@gmail.com>
To: Jeff King <peff@peff.net>, Eric Sunshine <sunshine@sunshineco.com>
Cc: Git List <git@vger.kernel.org>,
Derrick Stolee <dstolee@microsoft.com>,
Jeffrey Walton <noloader@gmail.com>
Subject: Re: Git self test failure on Solaris 11.3
Date: Thu, 6 Jun 2019 21:03:58 -0400 [thread overview]
Message-ID: <0e75e5ed-3964-5027-1af3-23237674554c@gmail.com> (raw)
In-Reply-To: <20190606190503.GA3265@sigill.intra.peff.net>
On 6/6/2019 3:05 PM, Jeff King wrote:
> On Thu, Jun 06, 2019 at 03:00:00PM -0400, Eric Sunshine wrote:
>
>>> I can't reproduce the intermittent failure either on 2.21.0, or with
>>> v2.22.0-rc3.
>>
>> I can't reproduce it either on Jeff's Solaris box. Perhaps Jeff can
>> add "-v -x" to his automated build/test script in order to help
>> diagnose the problem if it occurs again.
>
> Jeff: try "--verbose-log -x" if you're doing this as part of an automated
> run. That will leave you nice logs in t/test-results without dumping it
> all (and in particular, if you run the tests in parallel, it will avoid
> interleaving output from various tests).
Please keep me posted with any updates with exactly which command failed.
These comparison tests are intended to catch surprising interactions, but
are not very narrow. We'll need to know the exact failure spot, and the
failure could take a few forms:
* The git command failed with an error.
* The midx-enabled and midx-disabled commands differ in output.
Between these two options and the different commands that could have failed,
it's hard to dig in without more to go on.
Thanks,
-Stolee
prev parent reply other threads:[~2019-06-07 1:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAH8yC8kynjwT8wbHYV0DpDaMX=AnfmXeOci3uYUnnfsvbq4iRg@mail.gmail.com>
[not found] ` <CAH8yC8knkXtBii9KhS2iUo908zTx_NyPUgXZhqdwmwEF7Gz8Jg@mail.gmail.com>
2019-06-06 17:18 ` Git self test failure on Solaris 11.3 Eric Sunshine
2019-06-06 17:35 ` Jeff King
2019-06-06 19:00 ` Eric Sunshine
2019-06-06 19:05 ` Jeff King
2019-06-07 1:03 ` Derrick Stolee [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=0e75e5ed-3964-5027-1af3-23237674554c@gmail.com \
--to=stolee@gmail.com \
--cc=dstolee@microsoft.com \
--cc=git@vger.kernel.org \
--cc=noloader@gmail.com \
--cc=peff@peff.net \
--cc=sunshine@sunshineco.com \
/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).