What you would like to be added?
When a Go E2E test fails, it’s currently hard to understand the root cause because the test output doesn’t include enough debugging information.
It would be helpful to automatically collect and print basic diagnostics (like pod logs, pod status, and events from the test namespace) when a test fails. This could be added using a failure hook (e.g., AfterEach) so it only runs on failures and doesn’t affect successful runs.
Why is this needed?
E2E tests run in CI where failures can be caused by environment issues like scheduling delays or pod startup problems. Without logs or events, debugging these failures takes extra time.
Recent flaky test discussions #3365, #3366 show how difficult it can be to diagnose failures. Adding basic diagnostics would make debugging faster and improve overall reliability.
Love this feature?
Give it a 👍 We prioritize the features with most 👍
What you would like to be added?
When a Go E2E test fails, it’s currently hard to understand the root cause because the test output doesn’t include enough debugging information.
It would be helpful to automatically collect and print basic diagnostics (like pod logs, pod status, and events from the test namespace) when a test fails. This could be added using a failure hook (e.g., AfterEach) so it only runs on failures and doesn’t affect successful runs.
Why is this needed?
E2E tests run in CI where failures can be caused by environment issues like scheduling delays or pod startup problems. Without logs or events, debugging these failures takes extra time.
Recent flaky test discussions #3365, #3366 show how difficult it can be to diagnose failures. Adding basic diagnostics would make debugging faster and improve overall reliability.
Love this feature?
Give it a 👍 We prioritize the features with most 👍