gh-107652: Fix CIFuzz build#110576
Conversation
hugovk
left a comment
There was a problem hiding this comment.
There's an error with this, please could you check?
Sorry, something went wrong.
illia-v
left a comment
There was a problem hiding this comment.
I'm sorry for the error. Thank you for the fix!
Sorry, something went wrong.
hugovk
left a comment
There was a problem hiding this comment.
Thanks!
Sorry, something went wrong.
|
Btw, I use https://explainshell.com/explain?cmd=grep+-qE all the time, can recommend for Thanks, everyone! |
Sorry, something went wrong.
|
I can verify that my C changes now trigger CIFuzz: #110573 |
Sorry, something went wrong.
|
#109854 was created before merging CIFuzz, it changed I updated it from Do you know why? |
Sorry, something went wrong.
|
@hugovk I guess it happened because the merge commit contained changes to the relevant files |
Sorry, something went wrong.
When CI job was skipped the job was failing: https://github.com/python/cpython/actions/runs/6459321247/job/17536559744?pr=110573
This happened because
run_cifuzzwas not set. Now we use the same logic as for other tools by setting it tofalseRefs #107653
Refs #107652