Skip to content

ci: add JUnit XML timing artifacts for test analysis #514

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
max-sixty merged 1 commit into from
Jan 10, 2026
Merged

ci: add JUnit XML timing artifacts for test analysis #514

max-sixty merged 1 commit into from
Jan 10, 2026

Conversation

@max-sixty
Copy link
Owner

@max-sixty max-sixty commented Jan 10, 2026

Summary

  • Move nextest env vars (NEXTEST_STATUS_LEVEL, NEXTEST_SUCCESS_OUTPUT) into .config/nextest.toml
  • Add JUnit XML output to capture per-test timing data
  • Upload timing artifacts per-OS in CI to diagnose slow Windows tests (~10 min)

Test plan

  • CI passes on all platforms
  • JUnit artifacts are uploaded for each OS
  • After merge, download artifacts and analyze test timing

This was written by Claude Code on behalf of max-sixty

@max-sixty @claude
ci: add JUnit XML timing artifacts for test analysis
86a65a3 
Move nextest env vars (status-level, success-output) into config file.
Add JUnit XML output to analyze per-test timing in CI.
Upload timing artifacts per-OS to diagnose slow Windows tests.

Co-Authored-By: Claude <[email protected]>
@max-sixty max-sixty merged commit 49a7df9 into main Jan 10, 2026
19 checks passed
@max-sixty max-sixty deleted the test-speed branch January 10, 2026 04:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@max-sixty