The error message in the JUnit xml result is not informative

[kubernetes-sigs]

The error message in the JUnit xml result is not informative

[amwat]

Now that we've split the testers into separate binaries, we can probably skip wrapping the Test phase into a Junit error (but that's only for use cases where the tester itself is generating it's own Junit.) For simple cases especially with the --test=exec most commands you'll run would be simple commands that won't generate Junit so we still need an overall pass/fail for the entire Test phase.

For up/down we definitely do need to improve the output there, we should be using metadata.NewJUnitError in the deployers in most places.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[chizhg]

/lifecycle frozen