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): check higher number of procs #11791

Closed
wants to merge 67 commits into from
Closed

test(e2e): check higher number of procs #11791

wants to merge 67 commits into from

Conversation

jakubdyszkiewicz
Copy link
Contributor

Motivation

Same as #11716 but this time not from fork so we can check our runners

Implementation information

Supporting documentation

Fix #XX

@jakubdyszkiewicz jakubdyszkiewicz added ci/run-full-matrix PR: Runs all possible e2e test combination (expensive use carefully) ci/verify-stability ci/verify-stability-merge-master labels Oct 17, 2024
@jakubdyszkiewicz jakubdyszkiewicz changed the title Check higher number of procs test(e2e): check higher number of procs Oct 17, 2024
Copy link
Contributor

github-actions bot commented Jan 6, 2025

Reviewer Checklist

🔍 Each of these sections need to be checked by the reviewer of the PR 🔍:
If something doesn't apply please check the box and add a justification if the reason is non obvious.

  • Is the PR title satisfactory? Is this part of a larger feature and should be grouped using > Changelog?
  • PR description is clear and complete. It Links to relevant issue as well as docs and UI issues
  • This will not break child repos: it doesn't hardcode values (.e.g "kumahq" as an image registry)
  • IPv6 is taken into account (.e.g: no string concatenation of host port)
  • Tests (Unit test, E2E tests, manual test on universal and k8s)
    • Don't forget ci/ labels to run additional/fewer tests
  • Does this contain a change that needs to be notified to users? In this case, UPGRADE.md should be updated.
  • Does it need to be backported according to the backporting policy? (this GH action will add "backport" label based on these file globs, if you want to prevent it from adding the "backport" label use no-backport-autolabel label)

@jakubdyszkiewicz
Copy link
Contributor Author

closing due to no activity and it's very easy to reconstruct. I don't have time to test it more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci/run-full-matrix PR: Runs all possible e2e test combination (expensive use carefully)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants