Test runner is a little too enthusiastic to not re-run tests

[catamorphism]

For example, I do:

make check-stage2-rustpkg TESTNAME=first_test

Then when I do:

make check-stage2-rustpkg TESTNAME=second_test

make reports "Nothing to be done" because I guess running the first test touched some file somewhere that tells the build system "all the tests have up-to-date results". But really, only one test has up-to-date results. I work around this by touching a source file, but that results in recompilation, which is annoying.

[brson]

The situation isn't ideal. rm tmp/*ok will reset the test state so the tests rerun though.

[thestinger]

Still an issue.

[huonw]

Still an issue; I guess this could be solved by the extra::test runner recording which tests it has run, but then it becomes stateful, which is unfortunate :( (and this would still require integration into the makefiles).

[steveklabnik]

Triage: still an issue.

[rasendubi]

Still an issue

[Mark-Simulacrum]

Closing. With rustbuild, it seems this issue is fixed.

touch src/librustdoc/lib.rs
./x.py test --stage 1 src/test/compile-fail --test-args xcrate-unit-struct
   => runs xcrate-unit-struct test
./x.py test --stage 1 src/test/compile-fail --test-args xcrate-private-by-
   => runs xcrate-private-by-default test
./x.py test --stage 1 src/test/compile-fail
   => ignores the two already-run tests (private-by-default and unit-struct).