-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Fuzzer fails to build memchr #9368
Comments
The job is failing to compile. We should resolve separately but I am disabling for now since it breaks pull requests. See #9368
@addisoncrump -- Any chance it's obvious to you why this started failing? |
The CI tells the truth 🕊️ : https://github.com/astral-sh/ruff/actions/runs/7390478731/job/20105487965#step:6:39 It seems that musl is being set somehow. |
Notably, it seems that the bin provided from binstall is a musl binary: https://github.com/astral-sh/ruff/actions/runs/7390478731/job/20105487965#step:5:39 At a guess, this is some weird "rust binary expects consistency" issue. I'll try to repro locally. |
Yup, just verified locally: building with the version provided by cargo-fuzz upstream causes a build failure as it expects musl. |
Nice, thank you. I was able to get CI passing by pinning to the previous minor: #9372 |
Resolved at record pace 🚀 I'll communicate upstream to try to resolve this there so we can remove the pinning. Don't close this issue yet? |
@addisoncrump Let us know when we're good to close the issue. |
You can close it this side, there's now a tracking issue upstream: taiki-e/install-action#352 |
Thanks! |
See https://github.com/astral-sh/ruff/actions/runs/7390478731/job/20105487965
The text was updated successfully, but these errors were encountered: