jonathanmetzman
jonathanmetzman
Sorry for this terribly late reply. Do you have any pointers to docs on neutral vs inprogress status on github actions?
Superseded by https://github.com/google/oss-fuzz/pull/12679
Hmmm...on the one hand this is an error that fires a lot, but it usually highlights a real issue.
https://pantheon.corp.google.com/errors/detail/CKOVw8L-wf7nKQ;time=P30D;locations=global?e=-13802955&mods=logs_tg_prod&project=clusterfuzz-external
See gs://clusterfuzz-builds-centipede/hwloc/ or fftw3. I think we should talk about whether we want to force centipede on new projects at this point, so I'm not sure the right move is...
Skia noticed this caused weird behavior where the old build (from April 2023) was used https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=71292 causing bugs to be filed for extremely old builds.
About [50 bugs were opened in the past few days for centipede](https://bugs.chromium.org/p/oss-fuzz/issues/list?q=centipede%20opened%3Etoday-5&can=1), [17 of which are security bugs](https://bugs.chromium.org/p/oss-fuzz/issues/list?q=centipede%20opened%3Etoday-5%20type%3Dbug-security&can=1) (usually there none) I think all of these are suspect.
This never landed because our k8s instances don't connect to redis
We should still try to do this.
I think we are a little to short staffed for this, but it's probably something we can do when we get our new hires. Hopefully we can do it before...