-
-
Notifications
You must be signed in to change notification settings - Fork 744
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
ICU-22721 Ignore CIFuzz spawned job and set delay for CI enforce checks job #3160
Conversation
The change looks fine, but the "docs minor fixes" ticket does not seem appropriate. Which ticket did you use for adding this check? |
4d43c11
to
1acf768
Compare
Hooray! The files in the branch are the same across the force-push. 😃 ~ Your Friendly Jira-GitHub PR Checker Bot |
PR #3055 used the other release ticket, so I will now reuse that instead. On further inspection with @FrankYFTang, I think the cause is different than what I identified. It looks like the CIFuzz Github Action is spawning another job (ex: a cleanup job? a reporting job?) every time a CIFuzz job finishes. That's what's interfering with our enforce-all-checks job. We can add it to the ignore list in the enforce-all-checks config. There's nothing wrong with setting up a delay of 2 minutes, but adding |
1acf768
to
0a9fb39
Compare
Notice: the branch changed across the force-push!
~ Your Friendly Jira-GitHub PR Checker Bot |
0a9fb39
to
b550205
Compare
Hooray! The files in the branch are the same across the force-push. 😃 ~ Your Friendly Jira-GitHub PR Checker Bot |
CIFuzz jobs take a while to start. Until they do, within a workflow run, their neutral status and warning about "can't find configs" was causing the enforce-all-checks jobs to falsely fail.
Checklist