← Challenges

Repository · challenges

While remediating a build-watchman-confirmed wedged kotlin.build run 0bf40faf for kompile-core,

View on GitHub ↗

While remediating a build-watchman-confirmed wedged kotlin.build run 0bf40faf for kompile-core,

Reported (UTC): 2026-07-16 08:22

While remediating a build-watchman-confirmed wedged kotlin.build run 0bf40faf for kompile-core, the required production-server hierarchy could not use HardwareControlFabric because the documented default directory /home/helena/.config/hardware-control-fabric did not exist and the CLI failed exactly with Error: Certificate file not found: /home/helena/.config/hardware-control-fabric/fabric-client-cert.pem. Searching /home/helena found no alternate fabric certificates, forcing the last-resort SSH path. The prescribed command timeout 90 java -jar /root/ContainerNursery/apps/buildtest-cli.jar delete 0bf40faf did delete the run, as verified by the test-results API returning an empty array, but it emitted roughly 392000 tokens of unrelated P2P registry and gossip logging, kept running after the operation, and was terminated by timeout with exit code 124. Impact: the preferred auditable management path was unavailable, and the fallback deletion result was ambiguous until independently verified; the output also overwhelmed tool limits. Workaround: use read-only SSH stat to confirm the frozen test-events file, run the guarded delete command, verify deletion through the buildtest API, then rerequest the GitHub check suite. Durable fixes: provision the documented mTLS credentials in agent environments or update the skill with the real credential provider, and make buildtest-cli delete suppress unrelated P2P debug logs and shut down all background executors after returning an explicit success result.


Production verification — 2026-07-17

Status: STILL EXISTS. No merged fix, retired component, or live recovery evidence was found for this mechanism in the current GitHub and production checks; the record remains actionable rather than obsolete.

This record was retained because its underlying mechanism remains observable or its durable fix is still open; historical incident details above remain useful reproduction evidence.