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

test(e2e): disable amd64 self-hosted runners (backport of #11862) #11907

Closed
wants to merge 1 commit into from

Conversation

kumahq[bot]
Copy link
Contributor

@kumahq kumahq bot commented Oct 29, 2024

Automatic cherry-pick of #11862 for branch release-2.5

Generated by action

cherry-picked commit 31abdd6
⚠️ ⚠️ ⚠️ Conflicts happened when cherry-picking! ⚠️ ⚠️ ⚠️

On branch release-2.5
Your branch is up to date with 'origin/release-2.5'.

You are currently cherry-picking commit 31abdd66a.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   .github/workflows/build-test-distribute.yaml

no changes added to commit (use "git add" and/or "git commit -a")

IPV6 tests seems to be broken with our self-hosted runners.
It's not clear what's the problem, it can take some time to resolve it.
We'd rather have a slower CI with queues than CI which is broken. We can
still keep arm64 tests on self-hosted runners because those do not run
IPV6.

Signed-off-by: Jakub Dyszkiewicz <[email protected]>
@kumahq kumahq bot requested a review from a team as a code owner October 29, 2024 09:04
@kumahq kumahq bot requested review from michaelbeaumont and slonka and removed request for a team October 29, 2024 09:04
Copy link
Contributor

@slonka slonka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this isn't right, it should only change RUNNERS_BY_ARCH I think

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants