Re: [HACKERS] bin checks taking too long.

2014-12-23 Thread Noah Misch
On Tue, Dec 23, 2014 at 01:55:46PM -0500, Andrew Dunstan wrote: > On 12/23/2014 11:11 AM, Andrew Dunstan wrote: > > Use of uninitialized value $ENV{"top_builddir"} in concatenation (.) > > or string at t/001_start_stop.pl line 17. > > file not found: /src/test/regress/pg_regress at > >/home/b

Re: [HACKERS] bin checks taking too long.

2014-12-23 Thread Andrew Dunstan
On 12/23/2014 11:11 AM, Andrew Dunstan wrote: On 12/22/2014 10:41 PM, Peter Eisentraut wrote: On 12/22/14 7:56 PM, Andrew Dunstan wrote: Currently the buildfarm animal crake (my development instance) is running the bin check, but not any other animal. These tests still take for too long, not

Re: [HACKERS] bin checks taking too long.

2014-12-23 Thread Andrew Dunstan
On 12/22/2014 10:41 PM, Peter Eisentraut wrote: On 12/22/14 7:56 PM, Andrew Dunstan wrote: Currently the buildfarm animal crake (my development instance) is running the bin check, but not any other animal. These tests still take for too long, not least because each set of tests requires a separ

Re: [HACKERS] bin checks taking too long.

2014-12-22 Thread Peter Eisentraut
On 12/22/14 7:56 PM, Andrew Dunstan wrote: > Currently the buildfarm animal crake (my development instance) is > running the bin check, but not any other animal. These tests still take > for too long, not least because each set of tests requires a separate > install. You can avoid that by using ma

[HACKERS] bin checks taking too long.

2014-12-22 Thread Andrew Dunstan
Currently the buildfarm animal crake (my development instance) is running the bin check, but not any other animal. These tests still take for too long, not least because each set of tests requires a separate install. I have complained about this before, but we don't seem to have made any prog