Skip to content

Conversation

@williamjallen
Copy link
Collaborator

The build2test.timestatus column currently encodes information about both the binary "did this test instance pass the time check" and an aggregate across previous test instances indicating "does this chunk of tests represent a change in test time". This PR exposes just the former portion, returning a binary passed/failed value corresponding to the exact test record being retrieved. The rest of the information about aggregate test timing will be exposed via a separate field in the future.

Copy link
Member

@josephsnyder josephsnyder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Things look good! No problem with the GraphQL interactions but one question before approval:

In the Test Timing data that we have, "Time Status" not only has Pass/Fail but a Warning state in the GUI. This appears in the webpage even when the migration in this PR had been run.

Image

Should we introduce a Warning state?

Copy link
Member

@josephsnyder josephsnyder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the F2F! I think the plan ahead is solid and this is ready to go!

@josephsnyder josephsnyder added this pull request to the merge queue Oct 29, 2025
Merged via the queue into Kitware:master with commit 9746eb0 Oct 29, 2025
7 checks passed
@williamjallen williamjallen deleted the time-status-category branch October 29, 2025 13:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants