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: Collect sysdump as part of artifacts #25079
test: Collect sysdump as part of artifacts #25079
Conversation
af2d2a2
to
d361fe7
Compare
7478ee7
to
a1da1c9
Compare
Once we have a sysdump in the test artifacts a lot of files we collect will become duplicates. This commit however doesn't remove all those duplicate files from the test artifacts. Let's wait a bit and confirm the sysdump collection always work before cleaning things up. The sysdump collection was tested by making a test fail on purpose. Signed-off-by: Paul Chaignon <paul@cilium.io>
a1da1c9
to
7c1b797
Compare
/test-vagrant Job 'Cilium-PR-K8s-1.26-kernel-net-next' failed: Click to show.Test Name
Failure Output
Jenkins URL: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.26-kernel-net-next/2300/ If it is a flake and a GitHub issue doesn't already exist to track it, comment Then please upload the Jenkins artifacts to that issue. |
This test failed due to a connectivity blip when download Ubuntu packages: |
k8s-1.26-kernel-net-next failed with known flake #25411. Other CI jobs are passing. Marking ready to merge. |
Marking for backports to help debug CI flakes. We've confirmed for the past two weeks that it works in main and pull requests. |
Once we have a sysdump in the test artifacts a lot of files we collect will become duplicates. This commit however doesn't remove all those duplicate files from the test artifacts. Let's wait a bit and confirm the sysdump collection always work before cleaning things up.
The sysdump collection was tested by making a test fail on purpose. Test run: https://jenkins.cilium.io/view/PR/job/Cilium-PR-K8s-1.16-kernel-4.19/1461/.