From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: Is t5516 somehow flakey only on macOS?
Date: Fri, 08 Jan 2021 16:37:49 -0800 [thread overview]
Message-ID: <xmqq35zbgd2a.fsf@gitster.c.googlers.com> (raw)
I've seen this breakage only on "regular (osx-clang, clang,
macos-latest)" so far, but that does not necessarily mean clang on
macOS is miscompiling or anything like that.
https://github.com/git/git/runs/1671504998?check_suite_focus=true
What is frustrating is that the same CI/PR #1087 fully passes when
told to "Re-run jobs".
https://github.com/git/git/runs/1671626677?check_suite_focus=true
They are testing exactly the same commit 820e568 that has a tree
identical to that of ed0fd57b97 in seen in today's pushout.
Any interest in helping to find out what's going on from folks in
the macOS land?
Thanks.
next reply other threads:[~2021-01-09 0:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-09 0:37 Junio C Hamano [this message]
2021-01-09 9:11 ` Is t5516 somehow flakey only on macOS? Eric Sunshine
2021-01-09 10:34 ` Jeff King
2021-01-09 10:48 ` Jeff King
2021-01-09 10:57 ` Eric Sunshine
2021-01-09 17:33 ` SZEDER Gábor
2021-01-09 22:42 ` Junio C Hamano
2021-01-10 3:23 ` Jeff King
2021-01-09 22:29 ` 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=xmqq35zbgd2a.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
/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).