Re: Intermittent ECPG test failures on Windows buildfarm machines

From: Michael Meskes <meskes(at)postgresql(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Intermittent ECPG test failures on Windows buildfarm machines
Date: 2018-04-30 15:23:43
Message-ID: 16ce36fe63ca71a63007635517fa5f52a8a7634d.camel@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Am Montag, den 30.04.2018, 00:22 -0400 schrieb Tom Lane:
> Observe the following buildfarm failures:
> ...
> The common feature is that a single ECPG test case emitted an empty
> stdout
> file. There is no other indication of a problem: the corresponding
> stderr
> output files are correct (and no, the "correct" contents of those
> aren't
> empty), the test process exited with status zero, and there's no sign
> of
> an issue in the postmaster log. And it's a different test case each
> time.
>
> Baffled ... any ideas?

AFAICT there were like 4 commits to ecpg in March that were also
backported to 9.6. And while some included changes to the test suite I
have no idea which, if any, might result in this kind of problem. Also
there was at least one change to the Windows build system that impacted
ecpg.

Is there anyone out there with a Windows system who could bisect the
tree and find which commit is the culprit? Or did we have any changes
to the buildfarm scripts that may be causing this?

Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! SF 49ers! Use Debian GNU/Linux, PostgreSQL

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2018-04-30 16:09:12 Re: Intermittent ECPG test failures on Windows buildfarm machines
Previous Message Adrien Nayrat 2018-04-30 14:35:07 Re: Explain buffers wrong counter with parallel plans