-
Notifications
You must be signed in to change notification settings - Fork 388
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
Fix the cause of failure of multiple kind job runs on same VM #6468
Conversation
dc8098b
to
aea2c7d
Compare
Several tests failed due to the change |
aea2c7d
to
b0371ac
Compare
It is working now. |
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
Was the original PR introducing support for custom build tags not tested? It feels like such an issue could have been caught with some basic testing.
+1, hope this is the last amendment. |
/test-all |
@KMAnju-2021 can you update the respective builders & test the latest kind jobs here? |
@jainpulkit22 can you add some description to #6010 for how to run tests using specific build tag? I wanted to try but didn't find clear docs about it. |
sure, we just need to provide --build-tag <BUILD_TAG> while invoking the ci/jenkins/test.sh script. |
/test-kind-ipv6-all |
/test-kind-ipv6-only-all |
/test-kind-ipv6-all |
/test-kind-ipv6-only-all |
/test-kind-ipv6-all |
b0371ac
to
8a79ef4
Compare
/test-kind-ipv6-all |
1 similar comment
/test-kind-ipv6-all |
/test-kind-ipv6-only-all |
8a79ef4
to
a73cc75
Compare
/test-kind-e2e |
1 similar comment
/test-kind-e2e |
This PR is stale because it has been open 90 days with no activity. Remove stale label or comment, or this will be closed in 90 days. You can add a label "lifecycle/frozen" to skip stale checking. |
@antoninbas can you merge this PR? |
Please check out Lan's question above |
@antoninbas @luolanzone this PR is also ready to merge. |
643f3e1
to
f3e5334
Compare
/test-all |
f3e5334
to
120507f
Compare
/test-all |
db9911c
to
293e7de
Compare
/test-all |
293e7de
to
3f6002f
Compare
/test-all |
/test-kind-flexible-ipam-e2e |
I noticed the flexible ipam e2e test is already covered by github workflow, so please ignore the jenkins job failure |
on same VM. There were three main causes of failure: 1) Overriding of DOCKER_IMG_VERSION in makefile. 2) Overriding of kubeconfig because of which, when we ran multiple e2e tests together it used the same kubeconfig which was present the default location, so multiple jobs used the same cluster and failed. 3) Cleanup of antrea images after test. Signed-off-by: Pulkit Jain <pulkit.jain@broadcom.com>
3f6002f
to
e69b02b
Compare
/skip-all |
There were three main causes of failure:
we ran multiple e2e tests together it used the
same kubeconfig which was present the default
location, so multiple jobs used the same cluster
and failed.
Refer #6446 for more details