Skip to content

Conversation

@carlocab
Copy link
Member

@carlocab carlocab commented Jul 28, 2025

  • Have you followed the guidelines for contributing?
  • Have you ensured that your commits follow the commit style guide?
  • Have you checked that there aren't other open pull requests for the same formula update/change?
  • Have you built your formula locally with HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
  • Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
  • Does your build pass brew audit --strict <formula> (after doing HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

Follow-up to #230431. This should fix the missing Intel macOS bottles.

@carlocab carlocab added the CI-no-bottles Merge without publishing bottles label Jul 28, 2025
@github-actions github-actions bot added the boost Boost use is a significant feature of the PR or issue label Jul 28, 2025
@carlocab carlocab added the CI-no-fail-fast Continue CI tests despite failing GitHub Actions matrix builds. label Jul 28, 2025
@carlocab carlocab force-pushed the vineyard-intel-macos branch 2 times, most recently from 8aa8ebb to cba10cd Compare July 28, 2025 12:48
@github-actions
Copy link
Contributor

@carlocab bottle request for vineyard failed.

@carlocab carlocab force-pushed the vineyard-intel-macos branch 8 times, most recently from 6b3bfe3 to 9d0a92e Compare July 29, 2025 14:43
@carlocab carlocab changed the title vineyard: try to debug macos test failure vineyard: extend sleep Jul 29, 2025
@carlocab carlocab removed the CI-no-bottles Merge without publishing bottles label Jul 29, 2025
@carlocab carlocab force-pushed the vineyard-intel-macos branch 2 times, most recently from ae5e379 to 04d7214 Compare July 29, 2025 14:59
I _think_ this should fix the Intel macOS failures.

Follow-up to #230431
@carlocab carlocab force-pushed the vineyard-intel-macos branch from 04d7214 to fb6f411 Compare July 29, 2025 15:06
@carlocab carlocab marked this pull request as ready for review July 29, 2025 15:45
@carlocab carlocab added the ready to merge PR can be merged once CI is green label Jul 29, 2025
@github-actions
Copy link
Contributor

🤖 An automated task has requested bottles to be published to this PR.

Caution

Please do not push to this PR branch before the bottle commits have been pushed, as this results in a state that is difficult to recover from. If you need to resolve a merge conflict, please use a merge commit. Do not force-push to this PR branch.

@github-actions github-actions bot added the CI-published-bottle-commits The commits for the built bottles have been pushed to the PR branch. label Jul 29, 2025
@BrewTestBot BrewTestBot enabled auto-merge July 29, 2025 16:30
@BrewTestBot BrewTestBot added this pull request to the merge queue Jul 29, 2025
Merged via the queue into main with commit e9970e4 Jul 29, 2025
22 checks passed
@BrewTestBot BrewTestBot deleted the vineyard-intel-macos branch July 29, 2025 16:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

boost Boost use is a significant feature of the PR or issue CI-no-fail-fast Continue CI tests despite failing GitHub Actions matrix builds. CI-published-bottle-commits The commits for the built bottles have been pushed to the PR branch. ready to merge PR can be merged once CI is green

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants