Repository navigation
[uss_qualifier/reports] Add sequence view timeline index page - #1815
Open
BenjaminPelletier wants to merge 1 commit into
Open
BenjaminPelletier wants to merge 1 commit into
BenjaminPelletier wants to merge 1 commit into
Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
With uss_qualifier now supporting parallel test suite action execution, it is sometimes important to be able to understand the timing of when test scenarios were executed relative to each other. This PR adds a timeline.html file to the uss_qualifier sequence view artifact that is effectively an alternate/additional index page to see how and when the test suite actions were executed. The presentation is a vertical timeline very similar to the benchmarker timeline artifact, so this PR first factors out the common timeline elements between the two pages before reusing them in the new artifact element.
Most of the content in this PR is AI-generated UI elements, so I would suggest the most effective way to review would be to observe the outputs visually. They can be found in the CI artifacts, or reproduced locally in not very much time. I inspected the new timeline page from an f3548_self_contained run, and the timeline artifact from a benchmarker minimal.jsonnet run. These are also the artifacts I would suggest looking at to start with for a more in-depth review. Screenshots from these artifacts:
Zoomed in horizontally to verify functionality from #1804 still works: