Skip to content

Migrate to Ginkgo 2 to get JUnit XML reports on Prow timeouts #4940

@maelvls

Description

@maelvls

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.

Expected:

correct

But we get this:

incorrect

We are aware that Ginkgo 2 is coming:

Screenshot 2022-03-13 at 13 48 42

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/cleanupCategorizes 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.

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions