Expand testgrids per test

[alculquicondor]

What would you like to be cleaned:

Currently, the testgrids for unit and integration tests only mark whether the entire suite passed or not.

• https://testgrid.k8s.io/sig-scheduling#pull-kueue-test-unit-main
• https://testgrid.k8s.io/sig-scheduling#pull-kueue-test-integration-main

It would useful to have rows for each test.

Why is this needed:

To be able to track flakiness of specific tests.

Notes:

I don't know how to achieve this, but here is where the presubmits are defined:

https://github.com/kubernetes/test-infra/blob/master/config/jobs/kubernetes-sigs/kueue/kueue-presubmits.yaml

[alculquicondor]

/help

[k8s-ci-robot]

@alculquicondor:
This request has been marked as needing help from a contributor.

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-help command.

In response to this:

/help

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/test-infra repository.

[alculquicondor]

It probably has to do with using the kubekins image https://github.com/kubernetes/test-infra/blob/0aef7a83d0f5d74467667e4d13eef2589c5d740d/config/jobs/kubernetes/sig-testing/make-test.yaml#L18

[alculquicondor]

Or producing a junit XML report 🤷

[BenTheElder]

junit xml, not kubekins

see for example https://github.com/kubernetes-sigs/kind/blob/b6bc112522651d98c81823df56b7afa511459a3b/hack/make-rules/test.sh / https://github.com/kubernetes/registry.k8s.io/blob/main/hack/make-rules/test.sh

[kannon92]

So if I'm reading this right, we need to generate junit-xml reports for our tests. How exactly do these artifacts get uploaded to testgrid?

@alculquicondor Since I will be opening a PR to testgrid once I get #421 merged, I'll experiment with junit for that and then apply these findings to the other tests?

[BenTheElder]

So if I'm reading this right, we need to generate junit-xml reports for our tests. How exactly do these artifacts get uploaded to testgrid?

Testgrid reads junit.xml artifacts from what the CI uploads ($ARTIFACTS directory).

[kannon92]

/assign @kannon92

[kannon92]

Hello @BenTheElder, thank you for your help. I believe I figured out how to add testgrid per test.

#423