Re: Failed test 'ANCIENT_DATE is up to date'

[Niels Thykier <niels@thykier.net>]

Jakub Wilk:
> These mails from Jenkins are not as helpful as they could be...
> 
>> See <https://jenkins.debian.net/job/lintian-tests_sid/755/changes>
> 
> There's nothing interesting directly on the page. It would be much
> better if the mail linked to:
> https://jenkins.debian.net/job/lintian-tests_sid/755/console
> 

Indeed (or fullConsole or whatever it is called)

>> [...truncated 4712 lines...]
>> pass tests::fields-indep-without-arch-indep
>> pass tests::fields-depends-general
>> pass tests::fields-maintainer
> ...
> 
> I can't recall a single time the lines the Jenkins mail quoted gave my
> any clue what is wrong. In this case the error (which was somewhere
> within these 4712 truncated lines) is:
> 

It does mention:

> Failed tests (1)
>     suite:scripts [Try: prove -lr -j24 t]
> [...]

Although I agree it is not as informative as:

> #   Failed test 'ANCIENT_DATE is up to date'
> #   at t/scripts/ancient-sv-date.t line 50.
> #     '1385040054'
> #         <
> #     '1384819200'
> # Looks like you failed 1 test of 2.
> t/scripts/ancient-sv-date.t ............................... Dubious,
> test returned 1 (wstat 256, 0x100)
> Failed 1/2 subtests

Do you have any particular desire for how we solve it?  The problem with
the "suite:scripts" tests is that we do not get output of individual
failures.

 * Should we omit the "pass <test>" lines when output is not a TTY?

Thanks,
~Niels