Skip to content

Upload nextest performance trace as a Github artifact#7211

Draft
Aaron1011 wants to merge 4 commits intomainfrom
aaron/upload-nextest-trace
Draft

Upload nextest performance trace as a Github artifact#7211
Aaron1011 wants to merge 4 commits intomainfrom
aaron/upload-nextest-trace

Conversation

@Aaron1011
Copy link
Copy Markdown
Member

@Aaron1011 Aaron1011 commented Apr 6, 2026

This will let us visualize the largest contributions to our total test execution time


Note

Medium Risk
CI-only workflow changes, but they touch many pipelines and add always-on nextest recording/artifact uploads which could fail or increase runtime/storage if misconfigured.

Overview
Enables recording and uploading cargo-nextest Chrome performance traces across CI test workflows to help diagnose slow tests.

Sets NEXTEST_EXPERIMENTAL_RECORD=1 in multiple workflows/containers and adds export-chrome-trace + actions/upload-artifact steps (or equivalent in Docker Compose runs) after test execution for ClickHouse/Postgres/endpoint/live/batch/cache/optimization runs. Also bumps the pinned taiki-e/install-action SHA used to install Rust tools.

Reviewed by Cursor Bugbot for commit 0b25f35. Bugbot is set up for automated code reviews on this repo. Configure here.

This will let us visualize the largest contributions to our
total test execution time
Copy link
Copy Markdown

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit ad21f3f. Configure here.

Comment thread .github/workflows/live-tests.yml Outdated
Aaron1011 and others added 2 commits April 6, 2026 16:52
…s job

The `store export-chrome-trace` subcommand requires `NEXTEST_EXPERIMENTAL_RECORD=1`.
Also adds trace export + upload for the live-tests Docker job (not just evaluation-tests).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@Aaron1011 Aaron1011 marked this pull request as draft April 6, 2026 21:43
The `store export-chrome-trace` subcommand requires recording to be enabled
via a user config file with `[experimental] record = true` and `[record] enabled = true`.
The env var `NEXTEST_EXPERIMENTAL_RECORD=1` only unlocks the `store` subcommand.

- Add `ci/nextest-record.toml` with recording config
- Set `NEXTEST_USER_CONFIG_FILE` in all workflow env blocks
- For Docker-based tests, create the config inline since the CI dir isn't mounted

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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.

1 participant