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: run verifier tests with proper Go toolchain version #27857

Merged
merged 1 commit into from
Sep 1, 2023

Conversation

tklauser
Copy link
Member

Currently, the verifier tests are built and run with whatever Go toolchain version the LVH images ship. To make sure these tests are run with the same Go toolchain version as the rest of the tests install a copy of that Go toolchain before running the test.

This wasn't caught in CI on #27820 because the verifier workflow wasn't run passed on the ariane exclusion list.

Reported-by: @julianwiedmann

@tklauser tklauser added kind/bug/CI This is a bug in the testing code. area/CI Continuous Integration testing issue or flake release-note/ci This PR makes changes to the CI. labels Aug 31, 2023
@tklauser tklauser requested review from a team as code owners August 31, 2023 16:57
@tklauser tklauser requested review from aspsk and brlbil August 31, 2023 16:57
@tklauser
Copy link
Member Author

/ci-verifier

@tklauser
Copy link
Member Author

/test

@tklauser
Copy link
Member Author

/test

Currently, the verifier tests are built and run with whatever Go
toolchain version the LVH images ship. To make sure these tests are run
with the same Go toolchain version as the rest of the tests install a
copy of that Go toolchain before running the test.

This wasn't caught in CI on #27820
because the verifier workflow wasn't run passed on the ariane exclusion
list.

Reported-by: Julian Wiedmann <jwi@isovalent.com>
Signed-off-by: Tobias Klauser <tobias@cilium.io>
@tklauser
Copy link
Member Author

/ci-verifier

@aanm aanm merged commit bb3eec4 into main Sep 1, 2023
46 of 52 checks passed
@aanm aanm deleted the pr/tklauser/ci-verifier branch September 1, 2023 07:29
@giorio94 giorio94 added needs-backport/1.12 needs-backport/1.13 This PR / issue needs backporting to the v1.13 branch needs-backport/1.14 This PR / issue needs backporting to the v1.14 branch labels Jan 23, 2024
@giorio94
Copy link
Member

Marked for backport to all stable branches (except v1.15 which already includes it), as we are starting to hit the same issue there too: https://github.com/cilium/cilium/actions/runs/7623179184/job/20762689062

@giorio94 giorio94 added backport-pending/1.14 The backport for Cilium 1.14.x for this PR is in progress. and removed needs-backport/1.14 This PR / issue needs backporting to the v1.14 branch labels Jan 23, 2024
@giorio94
Copy link
Member

Marked for backport to all stable branches (except v1.15 which already includes it), as we are starting to hit the same issue there too: https://github.com/cilium/cilium/actions/runs/7623179184/job/20762689062

The workflow does not appear to exist in v1.12 and v1.13. Removing the needs-backport label for these branches.

@giorio94 giorio94 removed needs-backport/1.12 needs-backport/1.13 This PR / issue needs backporting to the v1.13 branch labels Jan 23, 2024
@github-actions github-actions bot added backport-done/1.14 The backport for Cilium 1.14.x for this PR is done. and removed backport-pending/1.14 The backport for Cilium 1.14.x for this PR is in progress. labels Jan 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/CI Continuous Integration testing issue or flake backport-done/1.14 The backport for Cilium 1.14.x for this PR is done. kind/bug/CI This is a bug in the testing code. release-note/ci This PR makes changes to the CI.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants