Run homebrew CI locally

[hugocaillard]

Output of brew config

HOMEBREW_VERSION: 4.0.18-85-g16b2a14
ORIGIN: https://github.com/Homebrew/brew
HEAD: 16b2a14c9408140b04828462b660d30056421fdb
Last commit: 22 hours ago
Core tap origin: https://github.com/Homebrew/homebrew-core
Core tap HEAD: faa43e4d84466c71b4c6a2ba2e82f5f8eff80b57
Core tap last commit: 5 hours ago
Core tap branch: master
Core tap JSON: 19 May 11:12 UTC
HOMEBREW_PREFIX: /opt/homebrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_MAKE_JOBS: 10
Homebrew Ruby: 2.6.10 => /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby
CPU: 10-core 64-bit arm_firestorm_icestorm
Clang: 14.0.3 build 1403
Git: 2.40.1 => /opt/homebrew/bin/git
Curl: 7.87.0 => /usr/bin/curl
macOS: 13.3.1-arm64
CLT: 14.3.0.0.1.1679647830
Xcode: N/A
Rosetta 2: false

Output of brew doctor

/

Description of issue

Hello,

I'm trying to understand what is happening here: Homebrew/homebrew-core#130619 and here Homebrew/homebrew-core#131127. The CI fails and it's hard to understand what is actually happening.

I'd like to reproduce the issue locally, is it possible to run Homebrew's GitHub actions locally?
I've seen this tool call ask but I haven't been able to use it so far.

Thanks

Note: if you have another ideas on how to debug the build, I'm happy to hear as well 🙏

[dawidd6]

brew test-bot $FORMULA should get you going easily.

[hugocaillard]

Yes I updated the local clarinet.rb file with the version I want to test.

And I'm trying to run

HOMEBREW_NO_INSTALL_FROM_API=1 && brew test-bot clarinet --verbose

I tried with the flag --build-from-source but it leads to the error "Not building a bottle for clarinet because it has unbottled dependencie"

Anyway, I still haven't been able to reproduce the error happening in homebrew CI and I soon out of ideas to debug it

[carlocab]

Hmmm. Can you show the output of brew linkage clarinet after a successful build locally?

[hugocaillard]

Sure:

brew linkage clarinet

System libraries:
  /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
  /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
  /System/Library/Frameworks/Security.framework/Versions/A/Security
  /usr/lib/libSystem.B.dylib
  /usr/lib/libiconv.2.dylib

[hugocaillard]

Thanks for restarting the CI (I think someone did)

[gromgit]

Sidenote: I'm sure you already know this, but many others probably don't. This command:-

HOMEBREW_NO_INSTALL_FROM_API=1 && brew test-bot clarinet --verbose

sets the shell variable HOMEBREW_NO_INSTALL_FROM_API, and does not export it to your shell environment, so brew test-bot cannot see it.

You should instead run either:-

HOMEBREW_NO_INSTALL_FROM_API=1 brew test-bot clarinet --verbose

or:-

export HOMEBREW_NO_INSTALL_FROM_API=1; brew test-bot clarinet --verbose

both of which set the environment variable HOMEBREW_NO_INSTALL_FROM_API that brew test-bot does see. The only difference is that the first one sets the variable only for brew test-bot, while the second sets it for all subsequent commands as well.

[hugocaillard]

Update: We're now sure that the issue come from the Deno version we are embedding in Clarinet. Unfortunately, it will take us a bit time to fix it (upgrade Deno or get rid of it).
As a short term solution, it has been suggested (Homebrew/homebrew-core#131430 (comment)) to only build for macos 11-arm64 (and not for 12 and 13). This solution sound acceptable to me.

But I need some help/guidance to achieve it

[SMillerDev]

Homebrew formulae shouldn't embed other software available in Homebrew: https://docs.brew.sh/Acceptable-Formulae#stuff-that-requires-vendored-versions-of-homebrew-formulae

[hugocaillard]

Thanks for your answer @SMillerDev

Well I agree that the way we vendor Deno isn't the best design, and we plan on removing it in Q3, it'll take some time and efforts.
But we've been shipping it like it for months without issue (see v1.5.4). Until homebrew's CI started to break for unknow reasons (so far).

So we have new features and bug fixes to ship that are currently blocked because we can't pass the CI right now. So I'm looking for solutions in the meantime. And the one suggested (skip build for macos 12 and 13) sounds good to me

[hugocaillard]

Hello,

We are still having issue to release, although there have been a solution suggested but no follow-up. And I don't know how to proceed.
I really need some help.
Should I open an issue? Is it possible to have a chat with someone from the team?
Thank you.

Note: the issue doesn't really match with the original topic of this discussion but I'm stuck and don't what to do to get help from the team.

cc @Bo98 @SMillerDev @carlocab

[MikeMcQuaid]

Don't open an issue, people will reply here.

[hugocaillard]

OK thanks, I wasn't sure this was the best place.

Honestly I feel like the actual issue is being ignored

[MikeMcQuaid]

It's not being ignored, it's just this is an open source project run by volunteers and several people have tried to help as much as they can but we have many thousands of packages and far fewer maintainers and need to prioritise.

[hugocaillard]

Yes I know, and I'm grateful the help I had so far.
But we are stagnating.
I'd like to understand why something that used to work doesn't work anymore (and then maybe, work on solution on our side or with the homebrew team)