fix(ci): don't recurse submodules when bumping the engine pointer - #156
Merged
Conversation
TechEngine carries TechAPI back as a submodule, so `git submodule
update --recursive` follows that cycle — TechEngine/TechAPI/TechEngine/
TechAPI/… — re-fetching the million-file data tree at every level until
the runner dies with "No space left on device":
fatal: Unable to checkout '679e487…' in submodule path
'TechEngine/TechAPI/TechEngine/TechAPI/TechEngine/TechAPI/…'
Every bump-engine run has failed this way since 2026-08-03, which is
when the job started switching branches before touching the submodule
and so began re-resolving it from scratch. The submodule pointer has
not moved automatically since.
The gitlink being bumped is at this repo's top level; nothing below it
needs updating, so drop --recursive from both submodule commands.
Refs #1
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Every
bump-enginerun has failed since 2026-08-03 — 9 in a row. Before that date, every run succeeded.TechEngine carries TechAPI back as a submodule, so
git submodule update --recursivefollows that cycle and re-fetches the million-filedata/tree at every level until the runner's disk is gone:The cycle is not new; what changed on 2026-08-03 is that the job began switching branches (
git checkout -B develop origin/develop) before touching the submodule, so it re-resolves it from scratch instead of reusing whatactions/checkouthad already placed. That was my change, and it turned a latent cycle into a hard failure.Consequence: the TechEngine submodule pointer has not been bumped automatically for a week. The auto-sync described in
.claude/techengine_submodule_sync_spec.mdhas been silently dead.Change
Drop
--recursivefrom both submodule commands. The gitlink being bumped is at this repo's top level; nothing below it needs updating, and recursion can only ever walk back into the cycle.actions/checkoutalready usessubmodules: true(single level), which is correct and unchanged. TechEngine's own workflows use no recursive submodule commands, so nothing is needed on that side.Refs #1