Present build step failures in junit files?

[kubernetes]

Present build step failures in junit files?

[spxtr]

Agreed. Maybe not JUnit, they could also go in JSON files next to started/finished.json. We'd like to have download/untar k8s, cluster up, test, down, and resource check as separate checks..

[lavalamp]

JUnit is important, because it lets the existing tooling in e.g. the merge queue read it.

[spxtr]

Sure, sounds reasonable. It would also let our other tools read it without trouble.

[lavalamp]

I think this is important, without this the merge queue might not know to stop merging if there is something consistently wrong, but not reported in JUnit output anywhere.

[fejta]

@spxtr will you please move this logic into hack/e2e.go?

[spxtr]

Yep. This is something I would like to do in the very near future.

[spxtr]

I think this is pretty much done. There are still improvements to be made, but we should make separate issues for those.