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

Run arm64 e2e tests for every pull request rather than on nightly schedule #16893

Closed
jmhbnz opened this issue Nov 8, 2023 · 3 comments
Closed

Comments

@jmhbnz
Copy link
Member

jmhbnz commented Nov 8, 2023

What would you like to be added?

Recently in #16801 we introduced on demand github actions runners for the arm64 platform.

Having on demand runner infrastructure in place means we should now have enough capacity to begin running arm64 tests for every pull request.

We should update our .github/workflows/e2e-arm64-nightly.yaml workflow to switch from scheduled nightly runs to instead running on: [push, pull_request]: https://github.com/etcd-io/etcd/blob/main/.github/workflows/e2e-arm64-nightly.yaml#L7-L8

Why is this needed?

Gain greater confidence and samples of e2e tests running against arm64 cpu architecture.

Hopefully detect issues before pull requests are merged to main.

@mingli103
Copy link
Contributor

Hi @jmhbnz please assign this issue to me.

@jmhbnz
Copy link
Member Author

jmhbnz commented Nov 9, 2023

One further thought for this issue @mingli103. Now that we are moving to on: [push, pull_request] for the e2e arm64 workflow we can actually move away from having two separate files.

Currently we have:

  • .github/workflows/e2e-arm64-template.yaml - Shared template
  • .github/workflows/e2e-arm64-nightly.yaml - Runs template against both release-3.5 and main branches nightly.

Moving forward we can just rename .github/workflows/e2e-arm64-template.yaml to .github/workflows/e2e-arm64.yaml and delete the other file. We can then just make the template file a standard workflow that will run on pull request.

mingli103 added a commit to mingli103/etcd that referenced this issue Nov 15, 2023
…tcd-io#16912

KubeconNA 2023 Contribfest issue etcd-io#16893 . Recently in etcd-io#16801 we introduced on demand github actions runners for the arm64 platform. Having on demand runner infrastructure in place means we should now have enough capacity to begin running arm64 tests for every pull request. Currently we have:
.github/workflows/e2e-arm64-template.yaml - Shared template
.github/workflows/e2e-arm64-nightly.yaml - Runs template against both
release-3.5 and main branches nightly. Moving forward we can just rename
.github/workflows/e2e-arm64-template.yaml to
.github/workflows/e2e-arm64.yaml and delete the other file. We can then
just make the template file a standard workflow that will run on pull
request.

Signed-off-by: Ming Li <mli103hawk@gmail.com>
mingli103 added a commit to mingli103/etcd that referenced this issue Nov 18, 2023
…tcd-io#16912

KubeconNA 2023 Contribfest issue etcd-io#16893 . Recently in etcd-io#16801 we introduced on demand github actions runners for the arm64 platform. Having on demand runner infrastructure in place means we should now have enough capacity to begin running arm64 tests for every pull request. Currently we have:
.github/workflows/e2e-arm64-template.yaml - Shared template
.github/workflows/e2e-arm64-nightly.yaml - Runs template against both
release-3.5 and main branches nightly. Moving forward we can just rename
.github/workflows/e2e-arm64-template.yaml to
.github/workflows/e2e-arm64.yaml and delete the other file. We can then
just make the template file a standard workflow that will run on pull
request.

Signed-off-by: Ming Li <mli103hawk@gmail.com>
@jmhbnz
Copy link
Member Author

jmhbnz commented Nov 24, 2023

Closed as completed in #16950, thanks @mingli103 🙏🏻

@jmhbnz jmhbnz closed this as completed Nov 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants