Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Network-related errors encountered when bottling for Monterey #88329

Closed
65 tasks done
carlocab opened this issue Oct 30, 2021 · 6 comments
Closed
65 tasks done

Network-related errors encountered when bottling for Monterey #88329

carlocab opened this issue Oct 30, 2021 · 6 comments
Labels
12 Monterey is specifically affected help wanted Task(s) needing PRs from the community or maintainers outdated PR was locked due to age

Comments

@carlocab
Copy link
Member

carlocab commented Oct 30, 2021

I'd appreciate help looking into and fixing these. Please link related PRs below so I can update the list as needed. Thanks!

Checksum mismatches:

Homepage/tarball/resource/livecheck errors:

@carlocab carlocab added help wanted Task(s) needing PRs from the community or maintainers 12 Monterey is specifically affected labels Oct 30, 2021
@samford samford mentioned this issue Oct 30, 2021
6 tasks
@samford
Copy link
Member

samford commented Oct 30, 2021

However we handle the livecheck block for juman in #88309 will also apply to jumanpp. The ku-nlp/jumanpp GitHub repository contains tags for jumanpp but it doesn't have a tag for 1.02 (the latest version from the first-party website), so we can't use that as an alternative source at the moment.

The check for timidity works for me locally (macOS 12, ARM64), so this may be an intermittent failure or it may only fail on CI.

The same appears to be true for tnftp/tnftpd. The most recent version bump PR (#84466) failed brew audit --online on CI but fetching the stable URL seemingly worked locally at the time.

@carlocab
Copy link
Member Author

tnftp/tnftpd are consistently reproducible. There are a few failed runs posted in the Monterey bottling issue. You wouldn't happen to have HOMEBREW_FORCE_BREWED_CURL set, do you? I've found that makes a lot of livecheck (and various other) failures go away.

@samford
Copy link
Member

samford commented Oct 30, 2021

tnftp/tnftpd are consistently reproducible.

Locally or on CI? The former would be surprising but the latter is to be expected if the source of the issue is the same as juman/jumanpp on CI.

You wouldn't happen to have HOMEBREW_FORCE_BREWED_CURL set, do you?

I have brewed curl installed (not in my path) but don't have the HOMEBREW_FORCE_BREWED_CURL environment variable set, as it's important for me to see issues with system curl in livecheck.

@Moisan
Copy link
Member

Moisan commented Nov 4, 2021

cuba is hosted on a HTTP-only site. I wrote an email to the owner of the site and codebase asking if they plan to move to HTTPS. I couldn't find that codebase anywhere else. What would be outcome if they don't plan to change to HTTPS?

@carlocab
Copy link
Member Author

carlocab commented Nov 5, 2021

We could just use HTTP I think. We already do this for a bunch of formulae. (688, actually.)

carlocab added a commit to carlocab/homebrew-test-bot that referenced this issue Nov 12, 2021
Passing this flag to `test-bot` will omit the `--online` flag from
`brew audit`, and also skip `brew livecheck`.

This is useful for at least three cases:

1. Bottling on a new OS/architecture. These failures should probably not
   block this especially if the build/linkage/test and install audits
   succeeded.
2. Failures which seem to occur only in CI. (cf.
   Homebrew/homebrew-core#88329, Homebrew/homebrew-core#89042)
3. PRs which require revision bumps to multiple formulae. CI runs on
   these PRs often take a very long time, and this makes fixing these
   failures (which is sometimes not even possible) and then re-running
   CI very impractical.

The last point is a particularly sore pain point for me, because I find
few things more frustrating than waiting a long time for CI to run only
to find that dependent tests have been blocked because livecheck failed,
or because the audit failed because the stable tarball was not reachable
(despite the source build completing successfully).
@chenrui333 chenrui333 mentioned this issue Nov 16, 2021
6 tasks
@cho-m
Copy link
Member

cho-m commented Mar 31, 2022

Updated list with formulae that were bottled sometime between last issue update and now along with opening PRs for some of remaining.

The only ones left are jumanpp and ski.

Once those are done, should be able to close this tracker

@cho-m cho-m added the almost there PR is nearly ready to merge label Apr 2, 2022
@cho-m cho-m removed the almost there PR is nearly ready to merge label May 24, 2022
@cho-m cho-m closed this as completed May 24, 2022
@github-actions github-actions bot added the outdated PR was locked due to age label Jun 24, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 24, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
12 Monterey is specifically affected help wanted Task(s) needing PRs from the community or maintainers outdated PR was locked due to age
Projects
None yet
Development

No branches or pull requests

4 participants