Centralize stdout/stderr capture in init_env and make run-test.sh inherit unified log #199
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
This PR introduces a single, CI-friendly stdout/stderr capture mechanism that is enabled once in
init_env
and automatically used by both per-suite[run.sh](http://run.sh/)
and the top-level[run-test.sh](http://run-test.sh/)
. No changes are required in individual tests.What changed
init_env
tee
capture with idempotent guard (no double capture when scripts re-source).run-test.sh
init_env
first so the unified capture is active before spawning tests.[run.sh](http://run.sh/)
inherits the same environment.