exclude_wrapper = trueAlex KallamWe should add a comment and/or a TODO here.
I have added a comment here and in all of the manual exclusions that were tracked in crrev.com/c/7804294 and merged into this CL.
# because they are not supported by the wrapper and will be manuallyAlex Kallam```suggestion
# because they are not supported by the wrapper and will be manually
```
Done
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
Still LGTM with one last optional nit.
# - exclude_wrapper - do not apply the llvm wrapper for centipede builds[Optional] Now that I see what this looks like on random `fuzzer_test` targets, I find `exclude_wrapper` to be quite obtuse. Consider flipping the bit and renaming to `is_fuzztest_compatible`, which would be nicely consistent with `is_fuzzilli_compatible`.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +1 |
# - exclude_wrapper - do not apply the llvm wrapper for centipede builds[Optional] Now that I see what this looks like on random `fuzzer_test` targets, I find `exclude_wrapper` to be quite obtuse. Consider flipping the bit and renaming to `is_fuzztest_compatible`, which would be nicely consistent with `is_fuzzilli_compatible`.
Done. Hopefully this workaround is short-lived enough that the lack of `is_fuzztest_compatible = true` on other targets doesn't cause confusion.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |