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

Make IntegratedSnarlFinder the default again #2785

Merged
merged 5 commits into from
Jul 22, 2020
Merged

Conversation

adamnovak
Copy link
Member

This reverts commit 9e54402.

@glennhickey
Copy link
Contributor

@adamnovak can you please switch over deconstruct's snarl finder while you're at it?

@adamnovak adamnovak changed the title Revert "Go back to Cactus snarl finder for release" Make IntegratedSnarlFinder the default again May 15, 2020
@adamnovak
Copy link
Member Author

This is now failing because of a Mac Travis problem that also affects master.

That problem is in turn due to Protobuf's 3.12.3 version, the current version, meaning different things to different people, and Homebrew may or may not stop shipping it.

I'm not quite sure what to do about that. Maybe always rebuild the Protobufs if we see 3.12.3?

@adamnovak
Copy link
Member Author

The real problem for our CI was this: Homebrew/homebrew-core#58229

Homebrew changed which flavor of 3.12.3 they ship, but kept the version number at 3.12.3. So now we look, see out headers were generated by what appears to be the right Protobuf version, don't regenerate them, and fail.

When Homebrew shipped Homebrew/homebrew-core#58229 they broke our CI by shipping a Protobuf 3.12.3 that is not compatible with headers generated by the Protobuf 3.12.3 that they previously shipped.

Since this particular Protobuf version is still [actively on fire](protocolbuffers/protobuf#7632), if we're trying to use it we should just rebuild the headers with the Protobuf we actually have.
@adamnovak
Copy link
Member Author

Now because we have to rebuild everything that depends on the Protobuf headers, we're hitting the timeout on the build. This approach may not work for Travis; maybe we just need to clear the caches instead.

We have to just ignore Proto 3.12.3 or we will rebuild completely multiple times.
@adamnovak
Copy link
Member Author

Yeah it turns out we can't clear out Protobuf headers every time we run make and still pass the Travis tests in time. I cleared the cache for this PR, but other busted PRs will need their caches cleared because I don't think we can usefully solve the problem via the build system.

@adamnovak adamnovak merged commit dc98ab2 into master Jul 22, 2020
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.

None yet

2 participants