mozilla/sccache - CodSpeed

sccache

Blog Docs Changelog

Performance History

Latest Results

build(deps): bump codecov/codecov-action from 5 to 6 Bumps [codecov/codecov-action](https://github.com/codecov/codecov-action) from 5 to 6. - [Release notes](https://github.com/codecov/codecov-action/releases) - [Changelog](https://github.com/codecov/codecov-action/blob/main/CHANGELOG.md) - [Commits](https://github.com/codecov/codecov-action/compare/v5...v6) --- updated-dependencies: - dependency-name: codecov/codecov-action dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>

dependabot/github_actions/codecov/codecov-action-6

22 hours ago

Fix missing basedirs implementation for multilevel, add tests

Felixoid:multiple-tiers-cache

4 days ago

build(deps): bump anyhow from 1.0.100 to 1.0.102

xtqqczze:deps/anyhow

6 days ago

chore(deps): update rust crate tar to v0.4.45

xtqqczze:deps/tar

6 days ago

Group tests logging in CI

main

6 days ago

fix: exclude CARGO_ENCODED_RUSTFLAGS from env var hash (#2651)

main

6 days ago

fix: exclude CARGO_ENCODED_RUSTFLAGS from env var hash For normal crate compilations, cargo consumes CARGO_ENCODED_RUSTFLAGS and passes the flags as command-line arguments to rustc. They are already hashed as part of the argument list (step 3), so hashing the env var is redundant. For build-script probe compilations (like proc-macro2's autocfg probes), the build script inherits the env var but does NOT pass those flags to its probe rustc invocation. The flags are irrelevant to the probe's output. Even if they passes it, it will then be in the argument list. In both cases, the env var value may contain build-specific paths, for example, `--remap-path-prefix=/random/build/path=...`. Those may cause unnecessary cache misses across builds.

weihanglo:encoded-rustflags

6 days ago

fix: exclude CARGO_ENCODED_RUSTFLAGS from env var hash For normal crate compilations, cargo consumes CARGO_ENCODED_RUSTFLAGS and passes the flags as command-line arguments to rustc. They are already hashed as part of the argument list (step 3), so hashing the env var is redundant. For build-script probe compilations (like proc-macro2's autocfg probes), the build script inherits the env var but does NOT pass those flags to its probe rustc invocation. The flags are irrelevant to the probe's output. Even if they passes it, it will then be in the argument list. In both cases, the env var value may contain build-specific paths, for example, `--remap-path-prefix=/random/build/path=...`. Those may cause unnecessary cache misses across builds.

weihanglo:encoded-rustflags

6 days ago

Latest Branches

0%

build(deps): bump codecov/codecov-action from 5 to 6#2660

22 hours ago

a7c33c2

dependabot/github_actions/codecov/codecov-action-6

0%

Implement multiple tiers caching with fallback and backfilling#2581

8 days ago

a24dc69

Felixoid:multiple-tiers-cache

0%

build(deps): bump anyhow from 1.0.100 to 1.0.102#2656

6 days ago

0c1755f

xtqqczze:deps/anyhow

© 2026 CodSpeed Technology

Home Terms Privacy Docs