Skip to content

Conversation

@stuartc
Copy link
Member

@stuartc stuartc commented Oct 15, 2025

Description

Add automatic detection of stale CMake build caches that occur when:

  • Using git worktrees with copied dependencies
  • Moving or renaming the repository directory
  • Restoring from backup at a different path
  • Syncing code between machines with different paths

The detection scans all CMakeCache.txt files in dependencies and compares cached paths with current paths. When mismatches are found, it cleans CMake build directories, compiled native libraries, and rebar3 build artifacts to prevent compilation errors.

This particularly resolves crc32cer compilation failures but works generically for any CMake-based dependency regardless of build directory naming convention.

AI Usage

Please disclose how you've used AI in this work (it's cool, we just want to know!):

  • Code generation (copilot but not intellisense)
  • Learning or fact checking
  • Strategy / design
  • Optimisation / refactoring
  • Translation / spellchecking / doc gen
  • Other
  • I have not used AI

You can read more details in our Responsible AI Policy

Pre-submission checklist

  • I have performed a self-review of my code.
  • I have implemented and tested all related authorization policies. (e.g., :owner, :admin, :editor, :viewer)
  • I have updated the changelog.
  • I have ticked a box in "AI usage" in this PR

Add automatic detection of stale CMake build caches that occur when:
- Using git worktrees with copied dependencies
- Moving or renaming the repository directory
- Restoring from backup at a different path
- Syncing code between machines with different paths

The detection scans all CMakeCache.txt files in dependencies and
compares cached paths with current paths. When mismatches are found,
it cleans CMake build directories, compiled native libraries, and
rebar3 build artifacts to prevent compilation errors.

This particularly resolves crc32cer compilation failures but works
generically for any CMake-based dependency regardless of build
directory naming convention.
@stuartc stuartc self-assigned this Oct 15, 2025
@github-project-automation github-project-automation bot moved this to New Issues in v2 Oct 15, 2025
@codecov
Copy link

codecov bot commented Oct 15, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.41%. Comparing base (b4fa0e1) to head (470db7e).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3762   +/-   ##
=======================================
  Coverage   88.41%   88.41%           
=======================================
  Files         414      414           
  Lines       17895    17895           
=======================================
  Hits        15821    15821           
  Misses       2074     2074           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@stuartc stuartc merged commit 1d53fa5 into main Oct 15, 2025
8 checks passed
@stuartc stuartc deleted the clean_cmake_cache branch October 15, 2025 12:24
@github-project-automation github-project-automation bot moved this from New Issues to Done in v2 Oct 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants