Statistic testing mode (build-and-stat-test) performing one build and count test runs for each crate #819
Conversation
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
azhogin
force-pushed
the
azhogin/stat-testing
branch
4 times, most recently
from
55035d9 to
d86ac14
Compare
… count test runs for each crate
azhogin
force-pushed
the
azhogin/stat-testing
branch
from
d86ac14 to
1aeefbf
Compare
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.
Statistic testing records each test execution result and provides errors as a summary (aka "OOM x4 | Unknown x2").
For each crate and toolchain one
cargo buildand severalcargo tests is performed.Statistic mode is needed for parallel frontend testing.
Statistic testing is enabled by
build-and-stat-testmode withstat-runspecifier:cargo run -- define-ex --mode=build-and-stat-test --stat-run=5Regression in statistic testing mode is reported when new toolchain produces more errors then old toolchain:
Errors are reported as a summary ("tests: failed (unknown) x4 | timed out x1"):
Example html report (x5 test):
regressions_174_report.zip
Example html report (x10 test):
regressions_174_x10.zip