From: Junio C Hamano <gitster@pobox.com>
To: Jeff Hostetler <jeffhostetler@github.com>
Cc: git@vger.kernel.org
Subject: [CI]: Is t7527 known to be flakey?
Date: Thu, 19 Jan 2023 18:52:01 -0800 [thread overview]
Message-ID: <xmqqtu0lzzn2.fsf@gitster.g> (raw)
The said test failed its linux-musl job in its first attempt, but
re-running the failed job passed.
https://github.com/git/git/actions/runs/3963948890/jobs/6792356234
(seen@e096683 attempt #1 linux-musl)
https://github.com/git/git/actions/runs/3963948890/jobs/6792850313
(seen@e096683 attempt #2 linux-musl)
next reply other threads:[~2023-01-20 2:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 2:52 Junio C Hamano [this message]
2023-01-20 15:23 ` [CI]: Is t7527 known to be flakey? Jeff Hostetler
2023-01-20 15:40 ` Junio C Hamano
2023-01-21 10:23 ` SZEDER Gábor
2023-01-23 16:56 ` Jeff Hostetler
2023-01-23 18:12 ` SZEDER Gábor
2023-01-25 19:02 ` Jeff Hostetler
2023-01-25 21:12 ` SZEDER Gábor
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=xmqqtu0lzzn2.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jeffhostetler@github.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 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.