Conversation
This formula constantly causes CI failures in Go PRs (e.g. Homebrew#88775) because checking the weather makes a network call that returns 403. Let's replace the test with one that just checks the version. It's a bad test, but it's better than the flaky one.
This formula constantly causes CI failures in Go PRs (e.g. #88775) because checking the weather makes a network call that returns 403. Let's replace the test with one that just checks the version. It's a bad test, but it's better than the flaky one. Closes #88802. Signed-off-by: rui <rui@chenrui.dev> Signed-off-by: BrewTestBot <1589480+BrewTestBot@users.noreply.github.com>
|
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. To keep this pull request open, add a |
|
Should this be reopened? |
Most definitely; we need the newest Go version ;) |
Let me know if you need anyone to review the PRs for the build failures |
|
Hi - I'm just a homebrew user (albeit a Patreon contributing one). I don't really understand the way things are done, or if 6 days is long to wait for a point release - but the failures above (edit: they're below now!) look like timeouts? They're all failed between 391 and 2136 minutes. |
|
Well, nobody seems to have time to investigate and fix them. So nothing is happening. If you want to help you can check if these things also fail when you run the command on your own device (with the older Go) |
|
after hand-editing to 1.17.3 it worked fine for me maybe just kick off the test again? |
|
Please restart CI. |
|
I think only one formula was fixed so that wouldn't help much |
|
Here's a quick overview of all the (Intel-based) CI steps that are currently failing:
|
|
Several of the issues mentioned above are still unfixed, but none (including the fixed ones) seem related to the patch release (Full disclosure: I only looked at the Intel-based issues, not the M1/ARM-based ones.) |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
I already wrote a few comments above that this pull request is not the right place to continue this discussion and asked that this was moved to https://github.com/Homebrew/discussions/. It's also a shame that I have to remember you all our code of conduct: https://github.com/Homebrew/.github/blob/HEAD/CODE_OF_CONDUCT.md#code-of-conduct I locked the comments here, only maintainers can now write here. @andig first and last warning: please watch your tone. Thanks |
|
I re-opened this, as things should have hopefully calmed down. We can now continue on working on fixing the last tests to get this done. If we get the list #88775 (comment) done, we will re-run CI and have a look at what remains to be fixed. |
|
Looked into envoy: The Minitest assertion is not part of the envoy formula- not sure where that's coming from. Might already be fixed as part of bazel though. |
|
ship:
|
|
The hasura message is funny: It depends on node14, but complains about 17. No idea what to do there. Apart from those two it might be good time for restarting CI- everything else has direct fixes or might depend on those fixes. |
|
Apparently |
|
If you can rebase it while you're at it, I think this PR is due for a rerun. |
7cf398a to
a89c876
Compare
|
Rebased, updated the related URLs to |
|
As for ship: no feedback on the ticket, latest commit from Jan 21 |
|
New failures in ARM build, AMD didn't finish:
|
carlocab
left a comment
There was a problem hiding this comment.
This is a security release; let's move this along.
|
... and now, 1.17.5 is out... |
Created with
brew bump-formula-pr.resourceblocks may require updates.