Re: default result formats setting

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Emre Hasegeli <emre(at)hasegeli(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: default result formats setting
Date: 2021-03-21 19:02:58
Message-ID: 4e257056-8c1f-69ac-037c-86c4e2a2837b@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 19.03.21 15:55, Emre Hasegeli wrote:
> I applied the patch, tried running the test and got the following:
>
> rm -rf '/Users/hasegeli/Developer/postgres/src/test/modules/libpq_extended'/tmp_check
> /bin/sh ../../../../config/install-sh -c -d '/Users/hasegeli/Developer/postgres/src/test/modules/libpq_extended'/tmp_check
> cd . && TESTDIR='/Users/hasegeli/Developer/postgres/src/test/modules/libpq_extended' PATH="/Users/hasegeli/Developer/postgres/tmp_install/Users/hasegeli/.local/pgsql/bin:$PATH" DYLD_LIBRARY_PATH="/Users/hasegeli/Developer/postgres/tmp_install/Users/hasegeli/.local/pgsql/lib" PGPORT='65432' PG_REGRESS='/Users/hasegeli/Developer/postgres/src/test/modules/libpq_extended/../../../../src/test/regress/pg_regress' REGRESS_SHLIB='/Users/hasegeli/Developer/postgres/src/test/regress/regress.so' /usr/bin/prove -I ../../../../src/test/perl/ -I . t/*.pl
> t/001_result_format.pl .. # Looks like your test exited with 2 before it could output anything.
> t/001_result_format.pl .. Dubious, test returned 2 (wstat 512, 0x200)
> Failed 4/4 subtests
>
> Test Summary Report
> -------------------
> t/001_result_format.pl (Wstat: 512 Tests: 0 Failed: 0)
> Non-zero exit status: 2
> Parse errors: Bad plan. You planned 4 tests but ran 0.
>

Could you look into the log files in that test directory what is going
on? The test setup is closely modeled after
src/test/modules/libpq_pipeline/. Does that one run ok?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2021-03-21 19:07:12 Re: ALTER TABLE .. DETACH PARTITION CONCURRENTLY
Previous Message Tom Lane 2021-03-21 18:34:58 Re: Fix pg_upgrade to preserve datdba