git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] ci/install-depends: attempt to fix "brew cask" stuff

From
SZEDER Gábor <szeder.dev@gmail.com>
Date
Feb 1, 2021, 22:11 UTC
Message-ID
<20210201221130.GA1036595@szeder.dev>
In-Reply-To
<YAH/ME/YvesZBxfr@coredump.intra.peff.net>
On Fri, Jan 15, 2021 at 03:46:40PM -0500, Jeff King wrote:
Show 26 quoted lines
> On Fri, Jan 15, 2021 at 03:07:38PM -0500, Eric Sunshine wrote:
> 
> > On Fri, Jan 15, 2021 at 3:00 PM Jeff King <peff@peff.net> wrote:
> > > > -     brew cask install --no-quarantine perforce || {
> > > > +     brew install --cask --no-quarantine perforce || {
> > >
> > > On a related note, it feels like perforce is a frequent offender for
> > > triggering spurious failures (both for homebrew setup, but I have
> > > definitely seen racy/flaky failures from it as well). I am tempted to
> > > say it is not worth the trouble, but then I do not care at all about
> > > git-p4 myself in the first place, so I may be biased.
> > 
> > To be fair to 'perforce', though, the fault of this particular problem
> > is Homebrew, which doesn't seem to be all that concerned about
> > backward compatibility, at least in my experience. The single
> > Homebrew-related automation script I wrote for personal use has been
> > broken by arbitrary Homebrew changes frustratingly often over the last
> > three years.
> 
> Yeah, sorry, I should have been more precise in my language. None of
> this is perforce's fault at all. It is homebrew in this case, and in the
> racy cases it is probably our tests. But I do not feel like trying to
> debug those races for a tool I don't care much about.
> 
> I tried to dig up some failing logs as an example, but it's actually a
> bit hard to search for,

I keep an eye out for flaky test failures, because they are much more entertaining to hunt down than the "usual" bugs, but can't recall any involving Perforce in the last year, since 6026aff5bb (git-p4: cleanup better on error exit, 2020-01-29) fixed the last one I knew about.

> and it looks like logs get expired after a few
> months anyway.
Travis CI can still show our builds from mid-2016:
  https://travis-ci.org/github/git/git/builds/146233889
though I couldn't dig out our very first build.
Previous: Jeff KingNext: Philippe Blain
Message 9 of 14 in “ci/install-depends: attempt to fix "brew cask" stuff”
  1. ci/install-depends: attempt to fix "brew cask" stuffJunio C Hamano, Jan 15, 2021
  2. Junio C HamanoJan 15, 2021
  3. Eric SunshineJan 15, 2021
  4. Derrick StoleeJan 15, 2021
  5. Junio C HamanoJan 15, 2021
  6. Jeff KingJan 15, 2021
  7. Eric SunshineJan 15, 2021
  8. Jeff KingJan 15, 2021
  9. SZEDER GáborFeb 1, 2021
  10. Philippe BlainJan 24, 2021
  11. Junio C HamanoJan 24, 2021
  12. Taylor BlauJan 25, 2021
  13. Jeff KingJan 27, 2021
  14. Junio C HamanoJan 28, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.