Skip to content

don't crash on brew update#2138

Merged
alecjacobson merged 5 commits intomainfrom
alecjacobson/brew-fix
Jan 4, 2023
Merged

don't crash on brew update#2138
alecjacobson merged 5 commits intomainfrom
alecjacobson/brew-fix

Conversation

@alecjacobson
Copy link
Copy Markdown
Contributor

@alecjacobson alecjacobson commented Jan 4, 2023

CI is failing because I think brew update is sending a failing exit code. https://github.com/libigl/libigl/actions/runs/3832188849/jobs/6522212468

It seems everything is continuing to install fine but it doesn't like that it can't create python links (which I don't believe we're using).

This fix (suggested here) just forces the update to return true. It seems that many others just run brew install ccache without brew update. Not sure if we still need brew update or if that was from when we used brew to get gmp and mpfr.

Another option would be to install ccache in some more reproducible way, but I don't have the bandwidth to figure that out at the moment.

@alecjacobson
Copy link
Copy Markdown
Contributor Author

huh. It's still failing. I guess I don't understand what's being run when. Is it failing on brew update or brew install ccache?

@alecjacobson
Copy link
Copy Markdown
Contributor Author

Ok, so after a bunch of experiments, it seems like the easiest fix is to just avoid running brew update. I'm not sure what the pitfalls of that are. brew update was pretty slow, too, so it's nice if we can avoid doing it.

The other PR is trying to download a ccache binary. But even if that works it seems inferior to using a package manager in some respects.

@alecjacobson
Copy link
Copy Markdown
Contributor Author

I'm going to go ahead and merge this for now so our CI continues. If I can grab @jdumas 's ear at some point maybe we can do something better.

@alecjacobson alecjacobson merged commit d91f4ed into main Jan 4, 2023
@alecjacobson alecjacobson deleted the alecjacobson/brew-fix branch January 4, 2023 18:02
@jdumas
Copy link
Copy Markdown
Collaborator

jdumas commented Jan 6, 2023

I think this solution is as good as any tbh.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants