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

Only build the fuzz crate on main #14478

Merged
merged 1 commit into from
Nov 20, 2024
Merged

Only build the fuzz crate on main #14478

merged 1 commit into from
Nov 20, 2024

Conversation

zanieb
Copy link
Member

@zanieb zanieb commented Nov 20, 2024

It's not actually doing anything per pull request and it's pretty slow? xref #14469

It seems useful to build on main still to find build regressions? e.g. #9368

@zanieb zanieb added the ci Related to internal CI tooling label Nov 20, 2024
@zanieb zanieb changed the title Only build the ruff crate on main Only build the fuzz crate on main Nov 20, 2024
@zanieb zanieb marked this pull request as ready for review November 20, 2024 05:05
Copy link
Member

@dhruvmanila dhruvmanila left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@zanieb zanieb merged commit 0dbcecc into main Nov 20, 2024
19 checks passed
@zanieb zanieb deleted the zb/fuzz-build branch November 20, 2024 05:07
Copy link
Contributor

ruff-ecosystem results

Linter (stable)

✅ ecosystem check detected no linter changes.

Linter (preview)

✅ ecosystem check detected no linter changes.

Formatter (stable)

✅ ecosystem check detected no format changes.

Formatter (preview)

✅ ecosystem check detected no format changes.

@MichaReiser
Copy link
Member

I generally found the fuzzer CI job useful because I never build the fuzzer locally. I often not even build the fuzzer locally when I break the build, instead I just push a fix and see if CI breaks now (because it requires some setup before you can build it successfully). That workflow no longer works.

I have never felt blocked by the fuzzer build. The slowest job, but very high signal, is the ecosystem check. That's what I'm waiting for.

MichaReiser added a commit that referenced this pull request Dec 13, 2024
## Summary
This reverts #14478

I now broke main twice because I wasn't aware that the API was used by
the fuzzer.

## Test Plan
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci Related to internal CI tooling
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants