-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Migrate to Ginkgo 2 to get JUnit XML reports on Prow timeouts #4940
Copy link
Copy link
Closed
Labels
kind/cleanupCategorizes issue or PR as related to cleaning up code, process, or technical debt.Categorizes issue or PR as related to cleaning up code, process, or technical debt.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Milestone
Description
Currently, anytime the end-to-ends time out, Ginkgo does not produce any JUnit XML, meaning that the Prow UI doesn't show which tests have timed out.
But we get this:
We are aware that Ginkgo 2 is coming:
When reading MIGRATING_TO_V2.md, I noticed that the JUnit XML output has been fixed when a suite times out, as detailed in onsi/ginkgo#728 (comment).
I suggest that we proceed with the migration to Ginkgo 2.
/kind cleanup
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
kind/cleanupCategorizes issue or PR as related to cleaning up code, process, or technical debt.Categorizes issue or PR as related to cleaning up code, process, or technical debt.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.


