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-ipsec-upgrade: Drop no-missed-tail-calls exclusion #29325

Merged
merged 1 commit into from
Nov 22, 2023

Conversation

brb
Copy link
Member

@brb brb commented Nov 22, 2023

The issue got fixed by #29309.

The issue got fixed by #29309.

Signed-off-by: Martynas Pumputis <m@lambda.lt>
@brb brb added area/CI Continuous Integration testing issue or flake needs-backport/1.14 This PR / issue needs backporting to the v1.14 branch labels Nov 22, 2023
@maintainer-s-little-helper maintainer-s-little-helper bot added dont-merge/needs-release-note-label The author needs to describe the release impact of these changes. labels Nov 22, 2023
@maintainer-s-little-helper maintainer-s-little-helper bot added this to Needs backport from main in 1.14.5 Nov 22, 2023
@brb
Copy link
Member Author

brb commented Nov 22, 2023

/ci-ipsec-upgrade

@brb brb added the release-note/ci This PR makes changes to the CI. label Nov 22, 2023
@maintainer-s-little-helper maintainer-s-little-helper bot removed the dont-merge/needs-release-note-label The author needs to describe the release impact of these changes. label Nov 22, 2023
@brb brb marked this pull request as ready for review November 22, 2023 14:26
@brb brb requested review from a team as code owners November 22, 2023 14:26
@brb brb added the ready-to-merge This PR has passed all tests and received consensus from code owners to merge. label Nov 22, 2023
@pchaigno pchaigno merged commit 9ecca98 into main Nov 22, 2023
50 checks passed
@pchaigno pchaigno deleted the pr/brb/ci-ipsec-upgrade-rm-missed-tail-calls branch November 22, 2023 15:41
@qmonnet
Copy link
Member

qmonnet commented Nov 27, 2023

@brb I see #29309 was backported to 1.13 as well. Should this commit be backported to 1.13 too?

@brb
Copy link
Member Author

brb commented Nov 28, 2023

@qmonnet I'm not sure about the v1.13 -> v1.12 downgrade, as the loader fix was backported only to v1.1{3,4}. Mind giving a go though? Maybe loading with iproute2 is more deterministic, so that we don't run into those cilium_calls vs cilium_call_policy issues.

@qmonnet
Copy link
Member

qmonnet commented Nov 28, 2023

Ah true we downgrade to 1.12 but the fix is not on that branch.
Yep I can still give it a try to see how it behaves.

@joamaki joamaki mentioned this pull request Nov 29, 2023
14 tasks
@joamaki joamaki 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 Nov 29, 2023
@maintainer-s-little-helper maintainer-s-little-helper bot moved this from Needs backport from main to Backport pending to v1.14 in 1.14.5 Nov 29, 2023
@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 Dec 1, 2023
@maintainer-s-little-helper maintainer-s-little-helper bot removed this from Backport pending to v1.14 in 1.14.5 Dec 1, 2023
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. ready-to-merge This PR has passed all tests and received consensus from code owners to merge. release-note/ci This PR makes changes to the CI.
Projects
No open projects
Status: Released
Development

Successfully merging this pull request may close these issues.

None yet

4 participants