From: Junio C Hamano <gitster@pobox.com>
To: Glen Choo <chooglen@google.com>
Cc: git@vger.kernel.org
Subject: Re: Is MacOS CI flaky?
Date: Fri, 16 Jun 2023 16:44:08 -0700 [thread overview]
Message-ID: <xmqqjzw3rn07.fsf@gitster.g> (raw)
In-Reply-To: <kl6lilbnrrl1.fsf@chooglen-macbookpro.roam.corp.google.com> (Glen Choo's message of "Fri, 16 Jun 2023 15:05:14 -0700")
Glen Choo <chooglen@google.com> writes:
> 1. https://github.com/chooglen/git/actions/runs/5294136258
>
> is just
>
> 2. https://github.com/chooglen/git/actions/runs/5292953535
>
> with a fix for "win build", but 2. also failed for completely unrelated
> reasons on osx-*.
>
> Casually clicking through https://github.com/git/git/actions/ suggests
> that others might be experiencing similar failures too?
>
> - https://github.com/git/git/actions/runs/5293250265
> - https://github.com/git/git/actions/runs/5289074140
One of the above two is a topic that mucks with credential seeing a
failure in http test, so I would not be surprised if the topic adds
a test that does not pass on macOS. Its breakage does seem somewhat
similar to what you are getting. I didn't check what the above
topic of yours is doing---maybe it is not touching http codepath
and/or the http tests at all? If that is the case, I would not be
surprised if the existing test is flaky.
The other one is failing tests with p4, which I saw is flaky and
fails to bring up or tear down p4 environment for testing. I
usually ignore them when I am watching the post-push tests, unless
at a major milestone, in which case I'd "Re-run failed jobs" and
sometimes the breakage goes away (i.e. the failure is flake).
Thanks.
next prev parent reply other threads:[~2023-06-16 23:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 22:05 Is MacOS CI flaky? Glen Choo
2023-06-16 23:44 ` Junio C Hamano [this message]
2023-06-17 4:42 ` Jeff King
2023-06-17 5:15 ` [PATCH] http: handle both "h2" and "h2h3" in curl info lines Jeff King
2023-06-17 5:31 ` Jeff King
2023-06-17 5:45 ` Jeff King
2023-06-17 8:07 ` Jeff King
2023-06-17 9:13 ` Junio C Hamano
2023-06-20 20:31 ` Glen Choo
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=xmqqjzw3rn07.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=chooglen@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.