Re: Failure with regression test largeobject if pg_regress invoked from external paths

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Failure with regression test largeobject if pg_regress invoked from external paths
Date: 2016-01-06 02:35:30
Message-ID: 3814.1452047730@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Michael Paquier <michael(dot)paquier(at)gmail(dot)com> writes:
> Today a colleague (Kingter Wang) has reminded me about a failure with
> the test case largeobject that can happen if pg_regress is run from an
> external path that has not results/ available at hand:

Um ... what exactly is the triggering condition here?

Your patch doesn't look unreasonable, but I don't have a lot of faith
in one-off fixes. If this test condition is something we ought to
support, it'd be better if the buildfarm were checking it someplace.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2016-01-06 03:14:29 Re: Failure with regression test largeobject if pg_regress invoked from external paths
Previous Message Michael Paquier 2016-01-06 01:50:56 Failure with regression test largeobject if pg_regress invoked from external paths