| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Postgres hackers <pgsql-hackers(at)postgresql(dot)org>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, a(dot)korotkov(at)postgrespro(dot)ru |
| Subject: | Broken and rotten TAP tests in contrib/bloom/ |
| Date: | 2018-11-26 02:51:25 |
| Message-ID: | 20181126025125.GH1776@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Alexander & Teodor,
It happens that the buildfarm machines do not like much the set of TAP
tests present in contrib/bloom/:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=longfin&dt=2018-11-25%2023%3A59%3A03
Here is an extract of the failure:
# Failed test 'initial: query result matches'
# at t/001_wal.pl line 38.
# got: '0|d
# 0|9
# 0|3
# 0|d
These currently cannot run within the buildfarm as a custom Makefile
target is used. And likely many developers don't run them either.
Could you look at what is wrong in them? Thanks,
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro HORIGUCHI | 2018-11-26 03:23:16 | Re: tab-completion debug print |
| Previous Message | Michael Paquier | 2018-11-26 02:21:15 | Re: pgsql: Add PGXS options to control TAP and isolation tests |