Re: seawasp failing, maybe in glibc allocator - Mailing list pgsql-hackers

From Fabien COELHO
Subject Re: seawasp failing, maybe in glibc allocator
Date
Msg-id alpine.DEB.2.22.394.2105101312470.494329@pseudo
Whole thread Raw
In response to Re: seawasp failing, maybe in glibc allocator  (Thomas Munro <thomas.munro@gmail.com>)
Responses Re: seawasp failing, maybe in glibc allocator
List pgsql-hackers
> And of course this time it succeeded :-)

Hmmm. ISTM that failures are on and off every few attempts.

> Just by the way, I noticed it takes ~40 minutes to compile.  Is there
> a reason you don't install ccache and set eg CC="ccache
> /path/to/clang", CXX="ccache /path/to/clang++", CLANG="ccache
> /path/to/clang"?  That doesn't seem to conflict with your goal of
> testing LLVM/Clang's main branch, because ccache checks the compiler's
> mtime as part of its cache invalidation strategy.

Yep.

I remember that I disactivated it for some reason once, but I cannot 
remember why. I just reactivated it, will see what happens.

-- 
Fabien.



pgsql-hackers by date:

Previous
From: ilmari@ilmari.org (Dagfinn Ilmari Mannsåker)
Date:
Subject: Re: Why do we have perl and sed versions of Gen_dummy_probes?
Next
From: Matthias van de Meent
Date:
Subject: Re: PG 14 release notes, first draft