| From: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Inadequate traces in TAP tests |
| Date: | 2017-03-20 13:12:05 |
| Message-ID: | bf97af9b-fd1d-fc29-def9-408efa501403@2ndQuadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
If you look at this failure case
<https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=jacana&dt=2017-03-19%2000%3A00%3A18>
you see:
t/002_pg_dump.........1..4449
# Looks like your test died before it could output anything.
dubious
Test returned status 255 (wstat 65280, 0xff00)
DIED. FAILED tests 1-4449
Failed 4449/4449 tests, 0.00% okay
That's really not helpful. We have no idea where things went wrong.
ISTM that the test setup and breakdown code, both in individual tests
and in PostgresNode.pm should be liberally sprinkled with diag() calls
to make it easier to narrow down errors..
Thoughts?
cheers
andrew
--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2017-03-20 13:16:56 | Re: Inadequate traces in TAP tests |
| Previous Message | Stephen Frost | 2017-03-20 13:11:52 | Re: Re: [COMMITTERS] pgsql: Improve pg_dump regression tests and code coverage |