Skip to content

[uss_qualifier/reports] Add timing report coloring and fix artifact generation pipeline#1346

Open
BenjaminPelletier wants to merge 1 commit intointeruss:mainfrom
BenjaminPelletier:timing-report-colors
Open

[uss_qualifier/reports] Add timing report coloring and fix artifact generation pipeline#1346
BenjaminPelletier wants to merge 1 commit intointeruss:mainfrom
BenjaminPelletier:timing-report-colors

Conversation

@BenjaminPelletier
Copy link
Member

This PR primarily adds severity coloring to the timing report artifact, but also addresses a number of issues in the artifact generation pipeline and various related user journeys:

  • Adds links to CI timing reports in github_pages
  • Adds timing report to dss_probing (to compare "pure" DSS tests to application tests that merely use a DSS)
  • Reworks make_artifacts.sh to more easily support the use case of the user having a report somewhere on their host machine, and wanting to generate artifacts somewhere (else) on their host machine (previously, it was difficult to figure out how to coordinate accessibility to the report input and artifact output between the container and host machine)
  • Enables generation of timing report artifacts from older reports by falling back to a new latest_timestamp property when end_time is not populated
  • Enables analysis of older reports by re-adding a deprecated placeholder for the SoloHappyPath test scenario

@BenjaminPelletier BenjaminPelletier marked this pull request as ready for review February 18, 2026 01:54
Copy link
Contributor

@mickmis mickmis left a comment

Choose a reason for hiding this comment

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

LGTM

try:
os.makedirs(output_path, exist_ok=True)
except PermissionError:
pass # This may be ok if writing directly to a single specific output folder provided to a container
Copy link
Contributor

Choose a reason for hiding this comment

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

Warn log the error?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants