Bug 16953 – auto-tester doesn't run rdmd_test (causes a number of regressions in each release)

from https://issues.dlang.org/show_bug.cgi?id=16952: >> Regarding the issue that this stuff comes up again and again: We do have a test in rdmd_test.d [1], and it does catch this. I think the problem is that the auto-tester doesn't run rdmd_test. and past related bugs: https://issues.dlang.org/show_bug.cgi?id=15175 rdmd --loop and --eval now complain about std.stream deprecation warnings https://issues.dlang.org/show_bug.cgi?id=13288 rdmd --eval fails because it still imports std.metastrings https://issues.dlang.org/show_bug.cgi?id=10352 Regression (2.063): --eval is broken in RDMD

FWIW, we do run the rdmd test suite via Travis (see https://github.com/dlang/tools/blob/master/travis.sh), but this only runs for PRs against the tools repository. We need to run the tests against PRs to all repositories to catch such issues effectively. We also have a daily cron job configured on Travis, so we can now at least be informed of such breakages shortly after they happen. Integrating the test into the auto-tester would be nice, however it currently doesn't test the tools repo at all. What might be more likely to happen instead is that I expand DAutoTest to also run the tools repository tests.

Since we now have buildkite, which does what Vladimir described, I think this can be considered solved.