-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
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).
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: