From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: "Han-Wen Nienhuys" <hanwen@google.com>,
"Avar Arnfjörð Bjarmason" <avarab@gmail.com>,
"ZheNing Hu" <adlternative@gmail.com>,
"Taylor Blau" <me@ttaylorr.com>
Subject: Re: CI: 'seen' minus a few passes tests, eh, almost
Date: Wed, 26 May 2021 14:32:19 +0900 [thread overview]
Message-ID: <xmqqzgwiawm4.fsf@gitster.g> (raw)
In-Reply-To: <xmqqcztecuy7.fsf@gitster.g> (Junio C. Hamano's message of "Wed, 26 May 2021 07:25:20 +0900")
Junio C Hamano <gitster@pobox.com> writes:
> It is sad that the tip of 'seen' rarely passes all tests these days.
>
> I excluded a few topics (chosen primarily by prejudice after looking
> at which tests failed earlier, without locating exactly where and
> why they fail) from 'seen' and the exclusion of them seems to have
> made 'seen' finally pass the tests, eh, almost [*1*].
> ...
> Excluded are:
>
> ab/fsck-unexpected-type
> hn/reftable
> hn/refs-errno-cleanup
> zh/ref-filter-raw-data
>
> ...
> [Footnote]
>
> *1* Except for "git repack" segfaults only in one of the tests:
>
> https://github.com/git/git/runs/2669668815?check_suite_focus=true#step:5:2846
Just with a hunch, I further excluded tb/multi-pack-bitmaps from
'seen', in addition to these four topics. It seems to pass the
whole test suite on both 32- and 64-bit build combinations.
https://github.com/git/git/actions/runs/877225207
Except that vs-build sometimes fails to download the sdk, that is.
next prev parent reply other threads:[~2021-05-26 5:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 22:25 CI: 'seen' minus a few passes tests, eh, almost Junio C Hamano
2021-05-26 5:32 ` Junio C Hamano [this message]
2021-05-26 6:07 ` Junio C Hamano
2021-05-26 14:39 ` Taylor Blau
2021-05-26 15:53 ` Jeff King
2021-05-26 16:48 ` Taylor Blau
2021-06-02 11:59 ` Johannes Schindelin
2021-05-26 15:02 ` ZheNing Hu
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=xmqqzgwiawm4.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=adlternative@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=hanwen@google.com \
--cc=me@ttaylorr.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).