-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
[CI] ok-to-test race condition #11490
Comments
/kind flake |
then doing a /retest would also work |
Ok, I hadn't realized this was integrated 👍
I spoke too soon, though. While a new pipeline was triggered and
succeeded, a failing context still appears on the PR page (only in at
the end of the "Conversation" pane, though, not in the "Checks") :
"Kubespray CI/pipeline" -> which links to the old failed PR with the
failed ci-not-authorzed.
I'll try a /retest on the PR to see if it changes anything
|
(Don't think it will though, @tico88612 tried that last week with no
resolution)
|
Yep, no changes :/
|
Another PR, #11540 |
are the /retest /retest-failed not working or they are working but don't resolve the issue ? |
On the next occurrence, ping me on slack without trying to retest/retry first. I'll check the logs |
Working, but failing to resolve the issue. I'm not completely sure, but it's possible that the trigger was using /ok-to-test in the PR description right away. |
Will do 👍 |
FYI: the one of the line is showing the variables sent to gitlab:
|
Apparently, if an org member create a PR and include /ok-to-test in the initial message, failfast will occasionnaly create two gitlab pipelines, both considered latest, but one fails the 'ci-authorized' test and prevent the PR status to be successful:
See the example here : #11489
/assign @ant31
/kind flake
The text was updated successfully, but these errors were encountered: