On Fri, Nov 21, 2025 at 11:48 PM Peter Eisentraut wrote:
> Currently, headerscheck and cpluspluscheck are very slow, and they
> defeat use of ccache. I have fixed that, and now they are much faster. :-)
>
> The problem was (I think) that the test files are created in a
> randomly-named directory
On 2025-Nov-21, Andres Freund wrote:
> On 2025-11-21 13:14:18 +0100, Álvaro Herrera wrote:
> > So how bad is the effect of the cache pollution that's now going to
> > occur?
>
> I don't think there's any cache pollution after this change - the
> pollution the comment was referencing was that cca
Hi,
On 2025-11-21 13:14:18 +0100, Álvaro Herrera wrote:
> On 2025-Nov-21, Peter Eisentraut wrote:
> ># Verify headerscheck / cpluspluscheck succeed
> >#
> > - # - Don't use ccache, the files are uncacheable, polluting ccache's
> > - # cache
>
> So how bad is the effect of the cache po
Hi,
On 2025-11-21 11:48:10 +0100, Peter Eisentraut wrote:
> Currently, headerscheck and cpluspluscheck are very slow, and they defeat
> use of ccache. I have fixed that, and now they are much faster. :-)
>
> The problem was (I think) that the test files are created in a
> randomly-named director
On 2025-Nov-21, Peter Eisentraut wrote:
> Currently, headerscheck and cpluspluscheck are very slow, and they defeat
> use of ccache. I have fixed that, and now they are much faster. :-)
Yeah, I had noticed this too. Thanks for fixing it.
> My solution is to create the test files in the build d
