-
Notifications
You must be signed in to change notification settings - Fork 254
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
🌱 Enable parallel testing in E2E #1527
Conversation
c1088c3
to
9f54163
Compare
/test metal3-bmo-e2e-test-pull |
9f54163
to
be82219
Compare
/test metal3-bmo-e2e-test-pull |
/test metal3-bmo-e2e-test-optional-pull |
be82219
to
a5de40e
Compare
/test metal3-bmo-e2e-test-pull |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor nits, and also a question.
3e6d58a
to
f57b2ba
Compare
/test metal3-bmo-e2e-test-pull |
f57b2ba
to
83f719e
Compare
/retest-required |
/test metal3-bmo-e2e-test-pull |
83f719e
to
f352b29
Compare
/test metal3-bmo-e2e-test-pull |
f352b29
to
f800ae7
Compare
/test metal3-bmo-e2e-test-pull |
73db2a9
to
6e61fbf
Compare
/test metal3-bmo-e2e-test-pull |
6e61fbf
to
9182085
Compare
/test metal3-bmo-e2e-test-pull |
aedcb30
to
0b33a8b
Compare
/test metal3-bmo-e2e-test-pull |
1 similar comment
/test metal3-bmo-e2e-test-pull |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Few nits.
38d59d0
to
3eddd70
Compare
Thanks a lot. I fixed them now. |
/test metal3-bmo-e2e-test-pull |
1 similar comment
/test metal3-bmo-e2e-test-pull |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok I'm happy with this if you can get the tests to pass!
I guess it is probably a matter of tweaking the intervals or we are a bit resource constrained in the Jenkins worker...
@mquhuy: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
3eddd70
to
c165bec
Compare
/test metal3-bmo-e2e-test-pull |
Thank you. I reckon using 2 VMs might be more likely to succeed, I just want to test if 3 VMs is feasible. I'll test it out a couple of times more to figure out. |
Signed-off-by: Huy Mai <[email protected]>
c165bec
to
934e18b
Compare
For reference, the workers we currently use have 8 CPU and 16 GB memory. We can change this later if we want 🙂 |
/test metal3-bmo-e2e-test-pull |
@lentzi90 I guess it explained the random flakes in the tests. 3 VMs would take 6 CPUs, so it means we have to run 3 threads for the tests on 2 remaining CPUs. Btw, could you help me override the integration tests? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
I don't have privileges to override context in this repo unfortunately
/override test-centos-e2e-integration-main test-ubuntu-integration-main |
@tuminoid: Overrode contexts on behalf of tuminoid: test-centos-e2e-integration-main, test-ubuntu-integration-main In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/cc @kashifest |
IMAGE_URL: "http://192.168.222.1/cirros-0.6.2-x86_64-disk.img" | ||
IMAGE_CHECKSUM: "c8fc807773e5354afe61636071771906" | ||
CERT_MANAGER_VERSION: "v1.13.1" | ||
SSH_CHECK_PROVISIONED: "true" | ||
IP_BMO_E2E_0: "192.168.222.122" | ||
SSH_PORT: "22" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do all tests pass without SSH_PORT
? It is used when checking to verify the node's boot source. Maybe it used 22 by default. But I think it would be good to still have it because the variable is used in the go code and someone might want to use another port sometime?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh NVM! I see that you have changed the code.
LGTM |
This is cool. Great work @mquhuy |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kashifest The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Fixes #1443