hack/verify-all should output the specific tests that failed

[robscott]

What would you like to be added:
When a test fails in hack/verify-all.sh, we should output the failed tests at the end of the run.

Why this is needed:
Debugging test logs is very complicated. For example, consider this recent failure where the output looked like this:

�[0;32mSUCCESS: hack/../hack/verify-yamllint.sh �[0m
make: *** [Makefile:113: verify] Error 1

The actual problematic logs were:

level=warning msg="[config_reader] The configuration option `linters.govet.check-shadowing` is deprecated. Please enable `shadow` instead, if you are not using `enable-all`."
conformance/tests/backendtlspolicy-normative.go:22: File is not `goimports`-ed with -local sigs.k8s.io/gateway-api (goimports)
	"k8s.io/apimachinery/pkg/types"
�[0;31mTest FAILED: hack/../hack/verify-golint.sh �[0m

It would be great to at least show the specific script that failed closer to the final output so it's more clear why make verify failed.

[robscott]

/help
/good-first-issue

[k8s-ci-robot]

@robscott:
This request has been marked as suitable for new contributors.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

/help
/good-first-issue

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[jgao1025]

The raw file is difficult to read.

Prow has a feature that it can only list the colored line in a build.log. Something like this - https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_gateway-api/3212/pull-gateway-api-verify/1825622946182336512.

I can easily locate all errors from there, and only the problem is it has a bug. It starts to list the wrong lines on the server side after I click Analyze button even I don't have any privilege; I don't see there is any way to recover this operation.

[TheInvincibleRalph]

Hi @robscott, I'd love to give this a shot.

[mlavacca]

/assign @TheInvincibleRalph