Carlo Marcelo Arenas Belón <carenas@xxxxxxxxx> writes: > On Thu, Apr 21, 2022 at 02:53:50PM +0200, Ævar Arnfjörð Bjarmason wrote: >> 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 > > Since the only reason why that is a concern is because it aborts the > rest of the run and is a recurring problem, wouldn't it be better to > tell the script to continue regardless and therefore skip all perforce > tests? > > Sure, there is a window where that integration could be broken which > will be only visible once the perforce cask gets fixed and perforce > installs again, but wouldn't that be less intrusive and overall safer > than the currently proposed change? Good suggestion. Care to come up with an alternative patch (or two)? Thanks.
