-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
fixes data race in system.Events and nil error logging #15665
Conversation
Please repush, since I added the [NO NEW TESTS NEEDED] flag. |
Signed-off-by: Harald Albrecht <[email protected]>
Thanks @thediveo |
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rhatdan, thediveo The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
just out of curiosity to better understand the processes: what's the "hold"? |
If test are still running or are red (failing) we use the hold to make sure this PR does not end up in the merge queue. While the merge bot will only merge the PR once all tests are green, it will for some reason still put it in the merge queue. The bot will merge PR in the same order as their are in the queue which means that no other PR can be merged in the meantime until this one was merged which can take a while due failing test. The hold will prevent us from having this problem. You can safely remove the hold once all tests are green until someone says otherwise. |
ah, thank you very much for the explanation! Re the failing checks, I'm unclear if the exact fails are even related to my small change:
How to move this forward? |
I click rerun on the test. Basically we have a ton of test which fail (flake) randomly. |
/hold cancel |
[NO NEW TESTS NEEDED]