-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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 Centipede compatible with as many existing projects as possible. #9583
Comments
Do you know why a lot of these are failing with compile_centipede doesn't exist. That's very bizarre |
I think librawspeed's issue is interesting. https://pantheon.corp.google.com/cloud-build/builds;region=us-central1/39202e47-3fb1-4646-9d22-38f0404901d8?project=oss-fuzz |
Related: #9299 |
Ah those are projects that are pinned to an older image |
upb and jwt-verify-lib may work now because of #9507 |
This allows these projects to be compiled with centipede Related: #9583
This allows these projects to be compiled with centipede Related: #9583
This allows these projects to be compiled with centipede Related: google#9583
It's pointless and has these drawbacks: 1. It add useless instrumentation not used by centipede that slows down the target 2. It adds instrumentation that expects an implementation at link time (__sancov_lowest_stack) which can break projects builds. Fixes google#9609 Related: google#9299 google#9583
Due to the large number of projects in OSS-Fuzz, this issue keeps track of projects that are/were incompatible with Centipede and how they are gradually made compatible by #9427.
The reason for incompatibility is collected and summarised in this spreadsheet.
The progress is tracked by this spreadsheet, where the columns are the commit IDs from #9427.
The text was updated successfully, but these errors were encountered: