Re: contrib/sepgsql regression tests have been broken for months - Mailing list pgsql-hackers

From Joe Conway
Subject Re: contrib/sepgsql regression tests have been broken for months
Date
Msg-id 66541690-91c2-48e6-9c99-12c9af25012b@joeconway.com
Whole thread Raw
In response to Re: contrib/sepgsql regression tests have been broken for months  (Joe Conway <mail@joeconway.com>)
Responses Re: contrib/sepgsql regression tests have been broken for months
List pgsql-hackers
On 10/28/25 18:49, Joe Conway wrote:
> On 10/28/25 18:20, Jacob Champion wrote:
>> On Tue, Oct 28, 2025 at 2:47 PM Joe Conway <mail@joeconway.com> wrote:
>>> I am not understanding why ssl_passphrase_callbackCheck is being run at
>>> all, but that is currently where I am stuck ¯\_(ツ)_/¯.
>> 
>> Old buildfarm client (REL_11). SSL tests aren't skipped until at least
>> 12, it looks like. (I ran into similar problems with OAuth recently.)
>> 
>> --Jacob
> 
> Thanks -- will give that a try!

Ok so that worked to an extent, and I have now reenabled rhino buildfarm 
cron job.

Everything < 18 passes.

18 and HEAD get this failure:
-----------------------------
# +++ tap check in contrib/sepgsql +++
#
# The SELinux boolean 'sepgsql_regression_test_mode' must be
# turned on in order to enable the rules necessary to run the
# regression tests.
#
# You can turn on this variable using the following commands:
#
#   $ sudo setsebool sepgsql_regression_test_mode on
#
# For security reasons, it is suggested that you turn off this
# variable when regression testing is complete and the associated
# rules are no longer needed.
-----------------------------

I believe the boolean is flipped in the 17 and below tests by the test 
script. How is that supposed to happen for the tap tests?


-- 
Joe Conway
PostgreSQL Contributors Team
Amazon Web Services: https://aws.amazon.com



pgsql-hackers by date:

Previous
From: Sami Imseih
Date:
Subject: Re: Bug in pg_stat_statements
Next
From: Andrew Dunstan
Date:
Subject: Re: Speed up COPY FROM text/CSV parsing using SIMD