From: "Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Philippe Blain <levraiphilippeblain@gmail.com>,
Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: [PATCH 0/2] ci: make the new GitHub workflow logic more defensive
Date: Sun, 11 Oct 2020 21:27:09 +0000 [thread overview]
Message-ID: <pull.748.git.1602451631.gitgitgadget@gmail.com> (raw)
Phil just reported that the check I added failed miserably
[https://github.com/phil-blain/git/runs/1238660958] in their fork, and the
entire run would be abandoned. That's totally unintended, and was caused by
a different metadata format for older recorded runs.
Let's work around this particular issue, and then make the entire check a
lot more robust.
This patch series is based on js/ci-ghwf-dedup-tests.
Johannes Schindelin (2):
ci: work around old records of GitHub runs
ci: make the "skip-if-redundant" check more defensive
.github/workflows/main.yml | 58 ++++++++++++++++++++------------------
1 file changed, 31 insertions(+), 27 deletions(-)
base-commit: 4463ce75b7eea47f9b484b05957def655d3f46d5
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-748%2Fdscho%2Fci-ghwf-dedup-tests-defensive-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-748/dscho/ci-ghwf-dedup-tests-defensive-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/748
--
gitgitgadget
next reply other threads:[~2020-10-11 21:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-11 21:27 Johannes Schindelin via GitGitGadget [this message]
2020-10-11 21:27 ` [PATCH 1/2] ci: work around old records of GitHub runs Johannes Schindelin via GitGitGadget
2020-10-11 21:27 ` [PATCH 2/2] ci: make the "skip-if-redundant" check more defensive Johannes Schindelin via GitGitGadget
2020-10-12 19:29 ` Junio C Hamano
2020-10-12 19:27 ` [PATCH 0/2] ci: make the new GitHub workflow logic " 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pull.748.git.1602451631.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=johannes.schindelin@gmx.de \
--cc=levraiphilippeblain@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).