Re: contrib/sepgsql regression tests have been broken for months
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Joe Conway <mail@joeconway.com>
Cc: Jacob Champion <jacob.champion@enterprisedb.com>,
pgsql-hackers@lists.postgresql.org
Date: 2025-10-29T23:12:26Z
Lists: pgsql-hackers
Joe Conway <mail@joeconway.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
Commits
-
Update expected output for contrib/sepgsql's regression tests.
- 67ef5575ccb0 18.1 landed
- 0758111f5d35 19 (unreleased) landed
-
Print out error position for some ALTER TABLE ALTER COLUMN type
- 65281391a937 18.0 cited