fix: improve maestro test output#652
Merged
Merged
Conversation
Size Report
Startup median (7 runs, lower is better):
Top changed chunks:
|
thymikee
force-pushed
the
codex/maestro-test-output-format
branch
from
0169cbe to
68576d5
Compare
|
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
Clean up
test --maestrooutput so non-verbose runs show concise PASS/FAIL rows instead of live lowercase progress lines.Keep step telemetry available in verbose/failure output, but drop redundant
[ok]markers and only include the attempt label when a later attempt is shown.Touched 3 files; scope stayed within CLI test output formatting.
Validation
Verified with the focused CLI network test and quick TypeScript validation:
pnpm exec vitest run src/__tests__/cli-network.test.ts --project unitpnpm check:quick