Bug#1123894: endless-sky: when integration tests fail, output is not shown in the log

[Simon McVittie]

Source: endless-sky
Version: 0.10.16-2
Severity: important
Tags: forky sid

If endless-sky fails its build-time tests (as in the FTFBS with 
sdl2-compat that I reported today), the build log has a summary, like 
this:

>Test project /build/reproducible-path/endless-sky-0.10.16/obj-x86_64-linux-gnu
>      Start  1: Abort Take Off On Excess Outfits In Cargo Warning
> 1/45 Test  #1: Abort Take Off On Excess Outfits In Cargo Warning ...***Failed    0.72 sec
...
>44/45 Test #87: Wormhole Navigation .................................***Failed    0.80 sec
>      Start 89: unit
>45/45 Test #89: unit ................................................   Passed    0.13 sec

but it doesn't display detailed output for the test-cases that failed.
This makes debugging a remote build failure considerably harder, and is
contrary to Policy §4.9:

    The package build should be as verbose as reasonably possible, except
    where the terse tag is included in DEB_BUILD_OPTIONS (see debian/rules
    and DEB_BUILD_OPTIONS). This makes life easier for porters and bug
    squashers more generally, who can look at build logs for possible
    problems. To accomplish this, debian/rules should pass to the commands
    it invokes options that cause them to produce verbose output.

I think it should be running `ctest --verbose`, similar to what 
/usr/share/perl5/Debian/Debhelper/Buildsystem/cmake.pm does. I'm testing 
a patch.

    smcv