Automatic Creation of issues for "Fuzzing build failure" not happening? #12536
Comments
|
I've noticed that this happend for the wasmtime project as well (in case another data point helps, otherwise sorry for the noise!) |
|
Thanks for your input! it is helpful indeed |
|
@DavidKorczynski any help or answer on the current issue? |
|
The root cause is due to this cronjob being broken, looking into it. |
|
There are some build failures which still point to monorail ids, which do not exist in buganizer. |
|
The cron ran successfully, new build errors should be notified once again. Keeping this open until folks confirm notifications are back. |
|
Great! Thanks @vitorguidi, I will update here if I receive any notification. |
|
I'm not sure if this is related, but wasmtime hasn't had any builds in the past 5 days. I can open a separate issue for this too if desired. |
A fix for this has been proposed/merged, see here: #12573 (comment) I was going to it another 24 hours before responding here: #12573 (comment) |
|
Thanks for the heads up! I'll cc myself to that issue and check in tomorrow too |
I don't think this is fixed. For example |
There were some hardcoded constants that needed to be updated for the Google Issue Tracker migration. We'll also stop adding the 'Project' custom field for now, because it's hard to propagate custom field values and it's not essential for build failure issues. This should hopefully fix google/oss-fuzz#12536 (comment).
### Motivation oss_fuzz_build_status and oss_fuzz_apply_ccs are broken due to buganizer rejecting emails without associated accounts. This serves as a workaround so at least some notifications can suceeed. (google/oss-fuzz#12536) ### Why this works Buganizer throws 400 errors listing out all rejected emails in the exception, so we can just parse the non gaia emails from that and complete the execution by ignoring those. ### Testing strategy Ran both cronjobs locally with the proposed new code, and verified they ran to completion.
|
@vitorguidi not sure if this is related to the issue, I have received two emails at same date and time for |
|
I think this one is fixed now and can be closed. Maybe a new thread can be created about the duplicate ones? |
|
This is probably due to me running the oss_fuzz_build_status locally more than once and the operation does not seem idempotent. This should not happen again, since the cronjob runs once daily. If this does happen again, please let us know. |
Hello,
As of recently, we had a build failure that lasted more than three days and we did not get a notification or an automatic issue created, is this by design? or is it related to migration from
bugs.chromium.org?This happened on Connectedhomeip project: https://oss-fuzz-build-logs.storage.googleapis.com/index.html#connectedhomeip
Thank you
The text was updated successfully, but these errors were encountered: