Skip to content
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

Open
VannTen opened this issue Aug 30, 2024 · 13 comments
Open

[CI] ok-to-test race condition #11490

VannTen opened this issue Aug 30, 2024 · 13 comments
Assignees
Labels
kind/flake Categorizes issue or PR as related to a flaky test.

Comments

@VannTen
Copy link
Contributor

VannTen commented Aug 30, 2024

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

@VannTen
Copy link
Contributor Author

VannTen commented Aug 30, 2024

/kind flake

@k8s-ci-robot k8s-ci-robot added the kind/flake Categorizes issue or PR as related to a flaky test. label Aug 30, 2024
@tico88612
Copy link
Member

@VannTen
Copy link
Contributor Author

VannTen commented Sep 10, 2024

Not sure how, but I managed to clear the stuck ci-not-authorized by restarting the whole pipeline from github by using "Re-run all checks" on the Check page of the PR (top right)
image

@ant31
Copy link
Contributor

ant31 commented Sep 10, 2024

then doing a /retest would also work

@VannTen
Copy link
Contributor Author

VannTen commented Sep 10, 2024 via email

@VannTen
Copy link
Contributor Author

VannTen commented Sep 10, 2024 via email

@VannTen
Copy link
Contributor Author

VannTen commented Sep 10, 2024 via email

@tico88612
Copy link
Member

Another PR, #11540

@ant31
Copy link
Contributor

ant31 commented Sep 23, 2024

are the /retest /retest-failed not working or they are working but don't resolve the issue ?

@ant31
Copy link
Contributor

ant31 commented Sep 23, 2024

On the next occurrence, ping me on slack without trying to retest/retry first. I'll check the logs

@VannTen
Copy link
Contributor Author

VannTen commented Sep 23, 2024

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.

@VannTen
Copy link
Contributor Author

VannTen commented Sep 23, 2024

On the next occurrence, ping me on slack without trying to retest/retry first. I'll check the logs

Will do 👍

@ant31
Copy link
Contributor

ant31 commented Sep 23, 2024

FYI: the Gitlab Sync job shows the logs of the sync between github / gitlab.
Those Logs are coming from the failfast-ci service directly.
e.g.
https://github.com/kubernetes-sigs/kubespray/pull/11540/checks?check_run_id=30415855924

one of the line is showing the variables sent to gitlab:

[INFO] Setting variables: {
'PR_LABELS': 'cncf-cla: yes,size/XS,ok-to-test,approved,release-note-none,dependencies', 
'EVENT': 'pull_request', 
'PR_ID': '11540',
 'SHA': '0f97c7a334c1811e4f7fdf6d83e3cd06ba3776e9', 
'SHA8': '0f97c7a3',
'FAILFASTCI_STATUS_API': 'https://ffci.kubespray.com/api/v1/github_status', 
'SOURCE_REF': 'dependabot/pip/ansible-9.10.0', 
'REF_NAME': 'dependabot/pip/ansible-9.10.0', 
'CI_REF': 'pr-11540-dependabot/pip/ansible-9.10.0', 
'GITHUB_REPO': 'kubernetes-sigs/kubespray'}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/flake Categorizes issue or PR as related to a flaky test.
Projects
None yet
Development

No branches or pull requests

4 participants