You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Produce warning if --message-format-version isn't specified, similar to cargo metadata without --format-version
Figure out situation around splitting vs combining stdout and stderr (may need to provide a little command-line configuration for this, e.g. --message-format-version 0.1,test-output=split)
Currently, --message-format libtest-json causes both the human and the machine-readable formats to be produced. We need something like Cargo's --message-format json and --message-format json-render-diagnostics.
Provide deserializers for the format in nextest-metadata
Switch integration tests over to this format (the ones in integration-tests/ scrape the current, unstable format, which sucks
Include messages for start-of-test-run and end-of-test-run (maybe only under the libtest-json-plus variant)
NEXTEST_EXPERIMENTAL_LIBTEST_JSON=1
in the environmentStill to do before stabilizing the format:
--message-format-version
isn't specified, similar tocargo metadata
without--format-version
--message-format-version 0.1,test-output=split
)--message-format libtest-json
causes both the human and the machine-readable formats to be produced. We need something like Cargo's--message-format json
and--message-format json-render-diagnostics
.integration-tests/
scrape the current, unstable format, which suckslibtest-json-plus
variant)cc @Jake-Shadle
The text was updated successfully, but these errors were encountered: