From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Junio C Hamano'" <gitster@pobox.com>
Cc: "'Max Kirillov'" <max@max630.net>,
"'SZEDER Gábor'" <szeder.dev@gmail.com>,
"'Johannes Schindelin'" <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org
Subject: RE: [ANNOUNCE] Git v2.21.0-rc1 (NonStop Results) - Good News
Date: Sat, 16 Feb 2019 13:24:23 -0500 [thread overview]
Message-ID: <000001d4c624$da8e05d0$8faa1170$@nexbridge.com> (raw)
In-Reply-To: <xmqqftsn4nik.fsf@gitster-ct.c.googlers.com>
On February 16, 2019 13:06, Junio C Hamano wrote:
> "Randall S. Becker" <rsbecker@nexbridge.com> writes:
> > On February 16, 2019 3:27, Max Kirillov wrote:
> >> What you could try is
> >> https://public-inbox.org/git/20181124093719.10705-1-
> max@max630.net/
> >> (I'm not sure it would not conflict by now), this would remove
> >> dependency between tests. If it helps it would be very valuable
> information.
> >
> > Good news. This patch does seem to do the trick. I wonder whether this
> > fixes the Azure build also.
> >
> > I have run the test under the following conditions:
> > Run 1 (system idle): Pass
> > Run 2 (system idle): Pass
> > Run 3 (system idle): Pass
> > Run 4 (system idle): Pass
> > Run 5 (system idle): Pass
> > Run 6 (system mild load, heavy file system): Pass Run 7 (system mild
> > load, moderate file system load - git fetch): Pass Run 8 (heavy system
> > load, heavy file system load): Pass Run 9 (--verbose, heavy system
> > load, heavy file system load): Pass Run 10 (GIT_TRACE=true, --verbose,
> > heavy system load, heavy file system
> > load): Pass
> > Run 11 (very heavy system load, very heavy file system load): Pass
>
> That indeed is a good news.
>
> > The current condition of the code is (the generate_zero_bytes delete
> > was previously removed so can be ignored for the patch):
>
> Just to make sure I do not misunderstand, this result is with Max's patch but
> without the generate_zero_bytes stuff?
Correct.
> Thanks, all. Hopefully we can get this test failures behind us before -rc2;
> knock, knock...
Once the fix is integrated and in the usual spots, I can verify with haste. The full test cycle is now at 50 hours (argh), which I will rerun in full at rc2, but this one is fast.
next prev parent reply other threads:[~2019-02-16 18:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-16 16:51 [ANNOUNCE] Git v2.21.0-rc1 (NonStop Results) - Good News Randall S. Becker
2019-02-16 17:02 ` Randall S. Becker
2019-02-16 18:05 ` Junio C Hamano
2019-02-16 18:24 ` Randall S. Becker [this message]
2019-02-16 18:57 ` Junio C Hamano
2019-02-18 18:45 ` Junio C Hamano
2019-02-18 18:50 ` Randall S. Becker
2019-02-19 10:05 ` Johannes Schindelin
2019-02-18 19:37 ` Johannes Schindelin
2019-02-18 21:57 ` Johannes Schindelin
2019-02-19 20:15 ` Max Kirillov
2019-02-19 20:36 ` Max Kirillov
2019-02-19 20:53 ` Randall S. Becker
2019-02-20 20:15 ` Johannes Schindelin
2019-02-18 20:24 ` Max Kirillov
2019-02-18 20:31 ` Randall S. Becker
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='000001d4c624$da8e05d0$8faa1170$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=max@max630.net \
--cc=szeder.dev@gmail.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).