Re: Strange corruption in psql output on mereswine

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, clarenceho(at)gmail(dot)com
Subject: Re: Strange corruption in psql output on mereswine
Date: 2018-11-09 03:36:18
Message-ID: 22621.1541734578@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> writes:
> The last two runs show strange but identical (?) corruption in psql
> output on mereswine (Debian on ARMv7):

> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mereswine&dt=2018-11-08%2009%3A10%3A14
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mereswine&dt=2018-11-07%2011%3A58%3A07

Note that the corruption is in the *expected* file, not the test result
file. I think this must mean that mereswine's git repo has become
corrupted. I'd recommend "rm -rf" on the repo and let the buildfarm
script pull down a fresh copy next time it runs.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2018-11-09 03:42:15 Re: Cache relation sizes?
Previous Message Amit Kapila 2018-11-09 03:11:48 Re: New function pg_stat_statements_reset_query() to reset statistics of a specific query