Re: Fixing cache pollution in the Kerberos test suite - Mailing list pgsql-hackers

From Jacob Champion
Subject Re: Fixing cache pollution in the Kerberos test suite
Date
Msg-id 4fd1ab76f968ca6953032a6a8a8a43c0847c9cbb.camel@vmware.com
Whole thread Raw
In response to Re: Fixing cache pollution in the Kerberos test suite  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Fixing cache pollution in the Kerberos test suite  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, 2021-01-25 at 14:36 -0500, Tom Lane wrote:
> However, this doesn't seem to explain why the test script isn't
> causing a global state change.  Whether the state is held in a
> file or the sssd daemon shouldn't matter, it seems like.
> 
> Also, it looks like the test causes /tmp/krb5cc_<uid> to get
> created or updated despite this setting.

Huh. I wonder, if you run `klist -A` after running the tests, do you
get anything more interesting? I am seeing a few bugs on Red Hat's
Bugzilla that center around strange KCM behavior [1]. But we're now
well outside my area of competence.

--Jacob

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1712875

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Fixing cache pollution in the Kerberos test suite
Next
From: Tom Lane
Date:
Subject: Re: Fixing cache pollution in the Kerberos test suite