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
People see the results of the final test run and think, "oh, good, 71 tests passed", but there are thousands of tests, and it would be nice to see all results at once. Difficult to implement though.
I've been thinking about this one. How about adding an option to the test framework to write out the test results to a file, in some serialised format. "make check" could then write each of these out to a file (which is cleaned by make clean), and then at the end run a python script to read them all in and summarise.
I'm happy to do this work if this design is sound?
In the long term I would for it all to be done in rust, but that requires getting dynamic loading working so that we can have one test runner load tests from multiple crates.
Activity
grahame commentedon Mar 31, 2012
I've been thinking about this one. How about adding an option to the test framework to write out the test results to a file, in some serialised format. "make check" could then write each of these out to a file (which is cleaned by make clean), and then at the end run a python script to read them all in and summarise.
I'm happy to do this work if this design is sound?
brson commentedon Apr 2, 2012
I am ok with this.
In the long term I would for it all to be done in rust, but that requires getting dynamic loading working so that we can have one test runner load tests from multiple crates.
Logfile output from tests; summarise in make check
z0w0 commentedon Apr 23, 2013
This appears to have been fixed in said pull request a while ago. Closing.
Merge pull request rust-lang#2075 from heiher/loong64-tests-avoid-con…
Merge rust-lang#2075
Auto merge of rust-lang#2075 - y86-dev:master, r=RalfJung