commit fa997e39aca00815da81e28c31dd231eb3c74f5f
Author: Sylvestre Ledru <sylvestre@debian.org>
Date: Wed Jun 24 12:34:29 2026 +0200
d/rules: keep sccache server alive (SCCACHE_IDLE_TIMEOUT=0) + use GCS cache on arm64
The libfuzzer step calls sccache directly with no backend env, long after the
server was started in configure. With the default 600s idle timeout the server
dies during the sccache-quiet final-link phase, so libfuzzer auto-spawns a
default-config server that writes to $HOME/.cache/sccache and fails with
HOME=/nonexistent. Set SCCACHE_IDLE_TIMEOUT=0 on both --start-server calls so
the configured server (GCS or local) stays up for the whole build. Also add
arm64 to the GCP arch filter so it uses the shared GCS cache like amd64.
Among the 90 debian patches available in version 1:22.1.8-1 of the package, we noticed the following issues:
![[bug history graph]](https://qa.debian.org/data/bts/graphs/l/llvm-toolchain-22.png){kind=link}