Upload nextest performance trace as a Github artifact#7211
Draft
Upload nextest performance trace as a Github artifact#7211
Conversation
This will let us visualize the largest contributions to our total test execution time
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ 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.
…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>
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>
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
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.

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-nextestChrome performance traces across CI test workflows to help diagnose slow tests.Sets
NEXTEST_EXPERIMENTAL_RECORD=1in multiple workflows/containers and addsexport-chrome-trace+actions/upload-artifactsteps (or equivalent in Docker Compose runs) after test execution for ClickHouse/Postgres/endpoint/live/batch/cache/optimization runs. Also bumps the pinnedtaiki-e/install-actionSHA 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.