Fixes:
Warning: Use lux instead of deprecated annie
Warning: Use prestodb instead of deprecated presto
Warning: Use openiothub-server instead of deprecated server-go
We often struggle with merging boost and icu4c updates due to merge
conflicts. The same occasionally happens with ffmpeg updates.
Let's make it easier to identify PRs that could potentially cause merge
conflicts with appropriate labels.
The newest version reported by Repology for these formulae is
inappropriate with respect to the formula. Since the `autobump`
workflow is now using `brew bump` to open version bump PRs and `bump`
uses the newest version from livecheck and Repology, we have to remove
these formulae from this list until we can tell `bump` to only open a
PR for a new version from livecheck.
Skipping testing dependents makes it that much harder to identify
formulae that need revision bumps.
See, for example, #91224, where the need to rebuild `gnuradio` could've
been identified days, if not weeks, earlier if we did not skip dependent
tests when one of the tested formulae fails.
Note that this will still skip the testing of dependents of failed
formulae, because these are passed in the `--skipped-or-failed-formulae`
flag.
Related discussion: #82220
We now use a `long build` label to identify PRs that need the
`CI-long-timeout` label but don't have it because other PRs are
currently using it.
Let's save some CI time by failing CI whenever a PR has the `long build`
label but not the `CI-long-timeout` label.
I've also updated `triage.yml` to add the `long build` label where
appropriate. The criterion I used here was whether a CI run that skips
dependent testing will still exceed the short timeout of 60 minutes.
This leaves out formulae that regularly take a long time only due to
having a large number of dependents (e.g. `python@3.*`, `go`). I think
this is the correct thing to do to avoid having to manually remove the
`long build` label every time the `triage` workflow is run in cases
where the CI run will not actually need `CI-long-timeout` (e.g. when we
use `CI-skip-dependents`).
This is based on the suggestion from #94792.
These don't need the outcome of the dependent tests, so let's show them
earlier. It'll also make the formulae step easier to distinguish from
the dependents step in the CI log.
* autobump: track more formulae
Signed-off-by: Rui Chen <rui@chenrui.dev>
* remove dups and add more rust formulae
Signed-off-by: Rui Chen <rui@chenrui.dev>
* fix case issue for `MeiliSearch` name
* autobump: remove `dwarfutils`
Co-authored-by: Sam Ford <1584702+samford@users.noreply.github.com>
* autobump: remove `fst`
Co-authored-by: Sam Ford <1584702+samford@users.noreply.github.com>
* autobump: remove `rover`
Co-authored-by: Sam Ford <1584702+samford@users.noreply.github.com>
Co-authored-by: Sam Ford <1584702+samford@users.noreply.github.com>
This is the same change as in #94067.
In particular, I need this in order to diagnose a bottling failure for
`libxslt` which I can't reproduce locally.
I got in touch with GitHub Support about our constantly failing GraphQL
queries. They requested for the `x-github-request-id` in the response
header of any of our failed queries, so I'm adding this to try to
generate one.
Bo Anderson
Sam Ford
Michka Popoff
Shaun Jackman
Alex
Carlo Cabrera
Mohammad Zulfikar
Xuehai Pan
BrewTestBot
Varun Sharma
Alexander Bayandin
Rui Chen
Mike McQuaid
Christian Clauss
Sean Molenaar
Thierry Moisan
rui
Dawid Dziurla