[Bug] Test E2E (kubectl-plugin) Has Different Buildkite Display Format

[tinaxfwu]

Search before asking

• I searched the issues and found no similar issues.

KubeRay Component

Others

What happened + What you expected to happen

Currently, most Buildkite go test logs follow a standardized format, for example:

- START:Running Autoscaler e2e (nightly operator) tests
- RUN TestRayClusterAutoscaler
- RUN TestRayClusterAutoscalerWithFakeGPU
- END:Autoscaler e2e (nightly operator) tests finished

However, the Test E2E (kubectl-plugin) suite uses gotestfmt, resulting in a different log style.

Reproduction script

Most tests use an AWK script (format.awk) to standardize their go test logs. For instance:
KUBERAY_TEST_TIMEOUT_SHORT=1m KUBERAY_TEST_TIMEOUT_MEDIUM=5m KUBERAY_TEST_TIMEOUT_LONG=10m go test -timeout 30m -v ./test/e2e | awk -f ../.buildkite/format.awk || (kubectl logs --tail -1 -l app.kubernetes.io/name=kuberay && exit 1)

The Test E2E (kubectl-plugin) suite is piped through gotestfmt
KUBERAY_TEST_TIMEOUT_SHORT=1m KUBERAY_TEST_TIMEOUT_MEDIUM=5m KUBERAY_TEST_TIMEOUT_LONG=10m go test -timeout 60m -v ./test/e2e -json 2>&1 | gotestfmt

Anything else

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

[tinaxfwu]

@MortalHappiness I created this issue and would like to contribute to it.
Here is the PR for this issue.