Re: headerscheck ccache support
Álvaro Herrera <alvherre@kurilemu.de>
From: Álvaro Herrera <alvherre@kurilemu.de>
To: Andres Freund <andres@anarazel.de>
Cc: Peter Eisentraut <peter@eisentraut.org>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2025-11-22T08:37:31Z
Lists: pgsql-hackers
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 ccache's cache would be > filled with entries for files that would *never* be used and would > therefore be useless. Ah, that makes sense. > With this change the added use of ccache will just accelerate the CI > runs, which I wouldn't consider polluting... Sure. -- Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/ "If you have nothing to say, maybe you need just the right tool to help you not say it." (New York Times, about Microsoft PowerPoint)
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
ci: Run headerscheck and cpluspluscheck in parallel
- 085a531983e2 19 (unreleased) landed
-
headerscheck ccache support
- 40bdd839f52a 19 (unreleased) landed
-
headerscheck: Use LLVM_CPPFLAGS
- d0b7a0b4c8f4 19 (unreleased) landed