ci: fix load test workflow paths - #304
Merged
Merged
Conversation
commit: |
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.
Summary
Fixes the manual load-test workflow after the harness moved to
tools/load-test.walking-togetherscenario in the workflow dispatch menuRoot cause
The workflow still referenced the previous root-level
load-testdirectory, so dependency installation, runner execution, and artifact collection could not find the harness outputs.Validation
cd tools/load-test && bun install --frozen-lockfilecd tools/load-test && bun testcd tools/load-test && bun src/runner.tsbun run load-test --git diff --checkNo remote load test was run.