From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com> To: git@vger.kernel.org Cc: "Junio C Hamano" <gitster@pobox.com>, "Eric Sunshine" <sunshine@sunshineco.com>, "Derrick Stolee" <stolee@gmail.com>, "SZEDER Gábor" <szeder.dev@gmail.com>, "Taylor Blau" <me@ttaylorr.com>, "Johannes Schindelin" <johannes.schindelin@gmx.de>, "Ævar Arnfjörð Bjarmason" <avarab@gmail.com> Subject: [PATCH 0/2] CI: don't fail OSX tests due to brew v.s. perforce.com mis-match Date: Thu, 21 Apr 2022 14:53:50 +0200 [thread overview] Message-ID: <cover-0.2-00000000000-20220421T124225Z-avarab@gmail.com> (raw) Junio: Despite modifying CI stuff this series merges cleanly with "seen", and has no semantic conflicts with any outstanding CI changes. For the past days we've again had CI failures due to "brew install" detecting a SHA-256 mismatch when trying to install the perforce package[1]. E.g. "seen" is now failing: https://github.com/git/git/runs/6104156856?check_suite_focus=true This occurrence of this issue will no doubt be fixed within a few days as the homebrew-cask repository is updated, i.e. this recipe: https://github.com/Homebrew/homebrew-cask/commits/master/Casks/perforce.rb But for our CI usage being this anal about the check isn't worth it, here's a passing CI run where we simply forced the installation: https://github.com/avar/git/runs/6092916675?check_suite_focus=true#step:3:87 and subsequently passed the git-p4 tests: https://github.com/avar/git/runs/6092916675?check_suite_focus=true#step:4:1678 Ævar Arnfjörð Bjarmason (2): CI: run "brew install perforce" without past workarounds CI: don't care about SHA256 mismatch on upstream "perforce" package ci/install-dependencies.sh | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) -- 2.36.0.893.g80a51c675f6
next reply other threads:[~2022-04-21 12:54 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-21 12:53 Ævar Arnfjörð Bjarmason [this message] 2022-04-21 12:53 ` [PATCH 1/2] CI: run "brew install perforce" without past workarounds Ævar Arnfjörð Bjarmason 2022-04-21 12:53 ` [PATCH 2/2] CI: don't care about SHA256 mismatch on upstream "perforce" package Ævar Arnfjörð Bjarmason 2022-04-21 20:47 ` Junio C Hamano 2022-04-21 21:08 ` Ævar Arnfjörð Bjarmason 2022-04-21 21:29 ` Eric Sunshine 2022-04-21 21:38 ` Junio C Hamano 2022-04-21 21:48 ` Eric Sunshine 2022-04-21 22:41 ` Junio C Hamano 2022-04-22 9:22 ` Ævar Arnfjörð Bjarmason 2022-04-21 21:30 ` [PATCH 0/2] CI: don't fail OSX tests due to brew v.s. perforce.com mis-matchy Carlo Marcelo Arenas Belón 2022-04-21 21:39 ` Junio C Hamano 2022-04-22 9:21 ` Ævar Arnfjörð Bjarmason 2022-04-21 21:57 ` [PATCH 0/2] CI: don't fail OSX tests due to brew v.s. perforce.com mis-match Junio C Hamano 2022-04-22 9:07 ` [PATCH v2 0/3] " Ævar Arnfjörð Bjarmason 2022-04-22 9:07 ` [PATCH v2 1/3] CI: run "brew install perforce" without past workarounds Ævar Arnfjörð Bjarmason 2022-04-22 9:52 ` Carlo Arenas 2022-04-22 18:46 ` Ævar Arnfjörð Bjarmason 2022-04-22 9:07 ` [PATCH v2 2/3] CI: don't care about SHA256 mismatch on upstream "perforce" package Ævar Arnfjörð Bjarmason 2022-04-22 11:15 ` Carlo Arenas 2022-04-22 9:07 ` [PATCH v2 3/3] CI: use https, not http to download binaries from perforce.com Ævar Arnfjörð Bjarmason
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=cover-0.2-00000000000-20220421T124225Z-avarab@gmail.com \ --to=avarab@gmail.com \ --cc=git@vger.kernel.org \ --cc=gitster@pobox.com \ --cc=johannes.schindelin@gmx.de \ --cc=me@ttaylorr.com \ --cc=stolee@gmail.com \ --cc=sunshine@sunshineco.com \ --cc=szeder.dev@gmail.com \ --subject='Re: [PATCH 0/2] CI: don'\''t fail OSX tests due to brew v.s. perforce.com mis-match' \ /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
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).