Re: Convert sepgsql tests to TAP - Mailing list pgsql-hackers
From | Andrew Dunstan |
---|---|
Subject | Re: Convert sepgsql tests to TAP |
Date | |
Msg-id | 9f62bd86-18f5-47f6-9526-14ea357d3ddc@dunslane.net Whole thread Raw |
In response to | Convert sepgsql tests to TAP (Peter Eisentraut <peter@eisentraut.org>) |
Responses |
Re: Convert sepgsql tests to TAP
|
List | pgsql-hackers |
On 2025-01-24 Fr 4:07 PM, Tom Lane wrote:
Andrew Dunstan <andrew@dunslane.net> writes:On 2025-01-24 Fr 10:57 AM, Tom Lane wrote:Looks like alligator needs some help here too.That's an issue with the new TAP test - alligator isn't running the TestSepgsql module. lapwing has also had a TAP test failure.Hmm. Neither of those animals should be trying to run the sepgsql test; they are not configured --with-selinux, and probably don't even have libselinux installed. Looking at the buildfarm client script, it looks to me like it will unconditionally try to run TAP tests in every contrib directory that has a "t" subdirectory. Up to now, none of those needed to be conditional ... but now we need some more awareness. However, if this theory is right, then pretty much every BF animal except rhinoceros should be failing. So there's some additional moving part that I'm not seeing. In any case, I think there's a BF client script bug here somewhere, or else these animals are running an old script version that does the wrong thing.
The new TAP test has:
+if (!$ENV{PG_TEST_EXTRA} || $ENV{PG_TEST_EXTRA} !~ /\bsepgsql\b/)
+{
+ plan skip_all =>
+ 'Potentially unsafe test sepgsql not enabled in PG_TEST_EXTRA';
+}
It looks like the error on alligator is coming from a NON TAP test:
rm -rf '/home/postgres/proj/build-farm-17/buildroot/HEAD/pgsql.build'/tmp_install /usr/bin/mkdir -p '/home/postgres/proj/build-farm-17/buildroot/HEAD/pgsql.build'/tmp_install/log make -C '../..' DESTDIR='/home/postgres/proj/build-farm-17/buildroot/HEAD/pgsql.build'/tmp_install install >'/home/postgres/proj/build-farm-17/buildroot/HEAD/pgsql.build'/tmp_install/log/install.log 2>&1 make -j1 checkprep >>'/home/postgres/proj/build-farm-17/buildroot/HEAD/pgsql.build'/tmp_install/log/install.log 2>&1 make: *** [../../src/Makefile.global:424: temp-install] Error 2 But why is it doing that? On my Ubuntu 22.04 dev instance, this test shows this as expected: echo "# +++ tap check in contrib/sepgsql +++" && rm -rf '/home/andrew/pgl/pg_head/root/HEAD/pgsql.build/contrib/sepgsql'/tmp_check && /usr/bin/mkdir -p '/home/andrew/pgl/pg_head/root/HEAD/pgsql.build/contrib/sepgsql'/tmp_check && cd /home/andrew/pgl/pg_head/contrib/sepgsql && TESTLOGDIR='/home/andrew/pgl/pg_head/root/HEAD/pgsql.build/contrib/sepgsql/tmp_check/log' TESTDATADIR='/home/andrew/pgl/pg_head/root/HEAD/pgsql.build/contrib/sepgsql/tmp_check' PATH="/home/andrew/pgl/pg_head/root/HEAD/pgsql.build/tmp_install/home/andrew/pgl/pg_head/root/HEAD/inst/bin:/home/andrew/pgl/pg_head/root/HEAD/pgsql.build/contrib/sepgsql:$PATH" LD_LIBRARY_PATH="/home/andrew/pgl/pg_head/root/HEAD/pgsql.build/tmp_install/home/andrew/pgl/pg_head/root/HEAD/inst/lib:$LD_LIBRARY_PATH" INITDB_TEMPLATE='/home/andrew/pgl/pg_head/root/HEAD/pgsql.build'/tmp_install/initdb-template PGPORT='65678' top_builddir='/home/andrew/pgl/pg_head/root/HEAD/pgsql.build/contrib/sepgsql/../..' PG_REGRESS='/home/andrew/pgl/pg_head/root/HEAD/pgsql.build/contrib/sepgsql/../../src/test/regress/pg_regress' share_contrib_dir='/home/andrew/pgl/pg_head/root/HEAD/pgsql.build/tmp_install/home/andrew/pgl/pg_head/root/HEAD/inst/share/postgresql/contrib' /usr/bin/prove -I /home/andrew/pgl/pg_head/src/test/perl/ -I /home/andrew/pgl/pg_head/contrib/sepgsql --timer t/*.pl # +++ tap check in contrib/sepgsql +++ [17:06:18] t/001_sepgsql.pl .. skipped: Potentially unsafe test sepgsql not enabled in PG_TEST_EXTRA [17:06:18] Files=1, Tests=0, 0 wallclock secs ( 0.00 usr 0.00 sys + 0.03 cusr 0.00 csys = 0.03 CPU) Result: NOTESTS log files for step contrib-sepgsqlCheck: ==~_~===-=-===~_~== /home/andrew/pgl/pg_head/root/HEAD/pgsql.build/contrib/sepgsql/tmp_check/log/regress_log_001_sepgsql ==~_~===-=-===~_~== [17:06:18.231](0.004s) 1..0 # SKIP Potentially unsafe test sepgsql not enabled in PG_TEST_EXTRA As of now I'm confused ... cheers andrew
-- Andrew Dunstan EDB: https://www.enterprisedb.com
pgsql-hackers by date: