-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
December 2021 edition of Myanmar Tools Build Failing #6978
Comments
The spirv-tools project is failing with a similar error:
|
related #6957 |
Pretty sure every project with AFL++ has been broken by this issue. Long term we might want to look into better build infra that can determine when a clang roll/other infra changes breaks things. |
I thought this was fixed yesterday by #6970 (comment). Apologies |
Not sure what went wrong there a second time in a row. Sorry, I thought I saw our build passing. Maybe OSS-Fuzz can switch to using only the latest release branche of clang? See #6974 (comment) |
Rebuilding base-images |
I checked locally that all of those pass:
Let's hope OSS-Fuzz is happy as well 🙏 |
Yup! https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=41876#c2 Thank you for the quick fix! |
Updates to the OSS Fuzz images frequently break the Myanmar Tools build:
Here is the latest edition:
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=41876
CC @jonathanmetzman @inferno-chromium
The text was updated successfully, but these errors were encountered: