Chain build failures traced to a full disk, not the code
satsuma-node is the software that runs Satsuma's chain, a standalone chain built with the Polkadot SDK. Each change to it is compiled and tested automatically by continuous integration on a GitHub-hosted runner. Those builds had been failing on the main line of work and on recent changes, and a fix to the build configuration was committed.
The session, run in Claude Code with Claude, traced the cause. "The CI failure on main and the last few PRs comes from the build itself." "The GitHub runner runs out of disk while compiling the node and the WASM runtime." The conclusion was short: "Nothing is wrong with the code."
The fix does two things. It frees about 25 GB by deleting tools the runner has preinstalled but the build never uses, among them .NET, the Android tools, GHC and CodeQL. And it compiles the whole dependency tree without debug info.
The first test run of the fix had just started when the session ended; a full run takes about 25 to 30 minutes. Whether the fix turns the main build green is not yet known.
- ci: free runner disk space and drop debug infoThe chain
- Diagnosing the build failure on the main line of satsuma-node
- Freeing disk on the build machine by removing unused preinstalled tools
- Building without debug info to cut disk use
- Treat the failure as a disk problem on the build machine, not a code problem
- Free about 25 GB by deleting unused preinstalled tools such as .NET, Android, GHC and CodeQL
- Drop debug info for the whole dependency tree
- The fix's first test run was unconfirmed; a full run takes about 25 to 30 minutes
- Whether the fix turns the main build green is not yet known
- An earlier change the failure had been attributed to could not be found in the repository