git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Eric Sunshine <sunshine@sunshineco.com>
To: Git List <git@vger.kernel.org>
Cc: Derrick Stolee <dstolee@microsoft.com>, Jeff King <peff@peff.net>,
	Jeffrey Walton <noloader@gmail.com>
Subject: Re: Git self test failure on Solaris 11.3
Date: Thu, 6 Jun 2019 13:18:01 -0400	[thread overview]
Message-ID: <CAPig+cS98DeSaF6pNqKCn6bAy=jjiTuc3AZpPB2cXm6hQ6vcqQ@mail.gmail.com> (raw)
In-Reply-To: <CAH8yC8knkXtBii9KhS2iUo908zTx_NyPUgXZhqdwmwEF7Gz8Jg@mail.gmail.com>

[forwarding to the Git list]

On Sun, Jun 2, 2019 at 6:23 AM Jeffrey Walton <noloader@gmail.com> wrote:
> On Sun, Jun 2, 2019 at 5:09 AM Jeffrey Walton <noloader@gmail.com> wrote:
> > I'm catching a self test failure on Solaris 11.3. Git 2.21 from sources.
> >
> > ok 8 - check normal git operations: two packs
> > ok 9 - add more packs
> > ok 10 - check normal git operations: mixed mode (two packs + extra)
> > ok 11 - write midx with twelve packs
> > not ok 12 - check normal git operations: twelve packs
> > #
> > #                       midx_git_two_modes "rev-list --objects --all" &&
> > #                       midx_git_two_modes "log --raw" &&
> > #                       midx_git_two_modes "count-objects --verbose" &&
> > #                       midx_git_two_modes "cat-file
> > --batch-all-objects --buffer --batch-check" &&
> > #                       midx_git_two_modes "cat-file
> > --batch-all-objects --buffer --batch-check --unsorted" sorted
> > #
> > ok 13 - verify multi-pack-index success
> > ok 14 - verify bad signature
> > ok 15 - verify bad version
> > ...
>
> Ick, this is bad. Intermittent failure. The second time around it passed.

Jeff Walton reported this to me privately. I'm not familiar with this
code and don't have time presently to investigate it, so I'm
forwarding it to the list in the hope that someone who knows the code
intimately (Stolee) or someone who has touched this code (Peff) might
have some idea about it. The failure is intermittent, so perhaps the
output of some command is not stable sort-wise(?).

       reply	other threads:[~2019-06-06 17:18 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   ` Eric Sunshine [this message]
2019-06-06 17:35     ` Git self test failure on Solaris 11.3 Jeff King
2019-06-06 19:00       ` Eric Sunshine
2019-06-06 19:05         ` Jeff King
2019-06-07  1:03           ` Derrick Stolee

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAPig+cS98DeSaF6pNqKCn6bAy=jjiTuc3AZpPB2cXm6hQ6vcqQ@mail.gmail.com' \
    --to=sunshine@sunshineco.com \
    --cc=dstolee@microsoft.com \
    --cc=git@vger.kernel.org \
    --cc=noloader@gmail.com \
    --cc=peff@peff.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).