Re: contrib/sepgsql regression tests have been broken for months

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Joe Conway <mail(at)joeconway(dot)com>
Cc: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: contrib/sepgsql regression tests have been broken for months
Date: 2025-10-29 23:12:26
Message-ID: 2919479.1761779546@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Joe Conway <mail(at)joeconway(dot)com> writes:
> Everything < 18 passes.

Hmm ...

> 18 and HEAD get this failure:

> # The SELinux boolean 'sepgsql_regression_test_mode' must be
> # turned on in order to enable the rules necessary to run the
> # regression tests.

> 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?

I'd be quite astonished if the buildfarm were trying to do anything
that requires root privilege, and even more astonished if it were
succeeding. I think the expectation is that you turned on
sepgsql_regression_test_mode manually before enabling this buildfarm
test. I don't understand how < 18 would be passing if it weren't on,
so the likely bet is that the test_sepgsql script is mistaken about
how it's checking that. Said script does work for me, but maybe
RHEL7's getsebool output is different from later versions?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David E. Wheeler 2025-10-29 23:13:32 Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()
Previous Message David Rowley 2025-10-29 23:07:08 Fix bogus use of "long" in aset.c