-
Notifications
You must be signed in to change notification settings - Fork 71
Export kind and cluster related logs under artifacts directory for e2e #451
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
Conversation
✅ Deploy Preview for kubernetes-sigs-lws canceled.
|
574d0fa
to
cec6956
Compare
Logs https://gcsweb.k8s.io/gcs/kubernetes-ci-logs/pr-logs/pull/kubernetes-sigs_lws/451/pull-lws-test-e2e-main-1-30/1902247411548426240/artifacts/ are collected correctly. This PR is ready for review. |
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.
I'm thinking whether we should make it a flag rather than exposing logs all the time, but let's find the root cause first.
/lgtm
/approve
Thanks!
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ardaguclu, kerthcet 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 |
That is a good point. What about we collect the logs if the exit code of ginkgo execution is non-zero?. That would be better in my opinion and I can open a followup PR. |
What type of PR is this?
/kind cleanup
What this PR does / why we need it
While investigating #437, I realized that there is almost no logs making the troubleshooting easier (e.g. https://gcsweb.k8s.io/gcs/kubernetes-ci-logs/pr-logs/pull/kubernetes-sigs_lws/445/pull-lws-test-e2e-main-1-31/1902041411415445504/artifacts/).
This PR exporting kind and cluster related logs under artifacts directory to troubleshoot any issues including the flaky one that I'm looking right now.
This PR mimics from jobset https://github.com/kubernetes-sigs/jobset/blob/15adf20ce9e0a10f01e7bcd8ea585a011814a2aa/hack/e2e-test.sh#L14-L17
Does this PR introduce a user-facing change?