cargo-nextest 0.9.146
Fixed Updated chacha20 and der to non-yanked versions.
Fixed Updated chacha20 and der to non-yanked versions.
Changed Configuration diagnostics now name the file each setting came from. For example, cargo nextest show-config version shows which file specified the nextest-version requirement, and cargo nextest show-config test-groups shows which file each override was defined in. For now, this is most useful when tool-specific config files are in play, but upcoming work to support local configuration files…
No content.
Changed Failures while setting up run recording (for example, a store directory that cannot be created) are now always reported as warnings, and the test run continues without recording. Previously, only a store format version mismatch was treated as a warning, and other setup failures aborted the run. This makes setup consistent with recording finalization, which already never fails a run. (#3547…
No content.
Added A new junit.report-skipped configuration setting controls which skipped tests are emitted in the JUnit XML report as <testcase> elements with a <skipped> child. (#885) Thanks to liangfu for your first contribution! While listing tests, nextest now shows a progress bar if listing takes longer than 2 seconds. Listing is usually fast, but can be slow in some environments, such as with antivirus…
No content.
Added A new junit.report-skipped configuration setting controls which skipped tests are emitted in the JUnit XML report as <testcase> elements with a <skipped> child. (#885) Thanks to liangfu for your first contribution! While listing tests, nextest now shows a progress bar if listing takes longer than 2 seconds. Listing is usually fast, but can be slow in some environments, such as with antivirus…
Added A new junit.report-skipped configuration setting controls which skipped tests are emitted in the JUnit XML report as <testcase> elements with a <skipped> child. (#885) Thanks to liangfu for your first contribution! While listing tests, nextest now shows a progress bar if listing takes longer than 2 seconds. Listing is usually fast, but can be slow in some environments, such as with antivirus…
Changed nextest-metadata updated to 0.15.0.
[nextest-runner] version 0.122.0
Added A new cargo nextest help <topic> subcommand renders reference documentation directly in the terminal. The available topics are: filterset (alias filtersets): the filterset DSL reference repo-config: the repository configuration reference user-config: the user configuration reference cargo nextest help lists the available topics. (#3419, #3424, #3432, #3433) Changed The glibc requirement for…
No content.
Changed Minor updates to the filterset reference.
This is a test release.
This is a test release.
No content.
[cargo-nextest] version 0.9.139
Added A top-level FILTERSET_REFERENCE_MD constant contains a filterset reference in Markdown format.
Added Nextest now sets the following environment variables during the list phase, not just the run phase: NEXTEST_VERSION NEXTEST_REQUIRED_VERSION NEXTEST_RECOMMENDED_VERSION NEXTEST_RUN_ID NEXTEST_BINARY_ID NEXTEST_WORKSPACE_ROOT This lets target runners and custom test harnesses use this information while listing tests. (#3410) Changed When --cargo-metadata is passed without --binaries-metadata,…
No content.
Changed CLI --help descriptions, configuration-reference docs, and JSON schema descriptions now use consistent language and voice. (#3366) Fixed Filterset expressions like not(test(foo)), all()and(test(foo)), and all()or(test(foo)), where not, and, or or is immediately followed by an opening parenthesis, now parse correctly. Previously, a separating space was required. (#3367)
Fixed Filterset expressions like not(test(foo)), all()and(test(foo)), and all()or(test(foo)), where not, and, or or is immediately followed by an opening parenthesis, now parse correctly. Previously, a separating space was required. (#3367)
No content.
Added Following up from the recently-added schema for repository configuration, nextest now also provides a JSON Schema for user configuration. The schema for the running version can be obtained by running cargo nextest self schema user-config. (#3351) Changed The max-progress-running user-config setting no longer accepts numeric strings like "8" (an undocumented fallback). The supported values re…
No content.
Fixed an issue with a from-crates.io build.
No content.
No content.