Let's improve the dmd tester.

[Seb]

On Thursday, 25 June 2020 at 14:39:18 UTC, Stefan Koch wrote:
> One thing which makes intrusive changes to DMD, hard to do, is 
> the testing "script".
> Which executes and evaluates tests for DMD.

You do realize that you can run all tests locally?
For example, `./test/run.d compilable` takes less than ten 
seconds on my machine.
You can also execute only individual tests e.g. `./test/run.d 
compilable/dtoh_enum.d`

> It greets you with a wall of text, in which passing and failing 
> tests are happily coexisting.

The tester ensures that the log output of each test isn't mixed.

> Which means that seeing which test failed for example on the 
> output of Ci service, in which you can't do a grep, is a 
> multi-second barrier in ones development process.

So to summarize your "wishes":

a) print error messages of failed tests at the end of the 
execution
BTW for local testing you can just rerun the test script. It will 
only rerun the failing tests.

b) hide messages for successful tests under the verbose flag

Did I understand you correctly?