Repository navigation
Close ISSUE-LOCAL-01M5ZEVF7HQ8SFK9F8A9WSREEP and record the row outcome - #3516
Merged
Merged
Conversation
The fix landed as f484c76 (PR localai-org#3515). The issue closes with the dated resolution evidence: the wall was the ubuntu-26.04 /tmp tmpfs, not root disk pressure; run 40637909804 proves the mask step green on agent-record and build-test-vulkan. The spec gains its ## Outcome: the rejected first hypothesis, the default values and why each holds, and what was left out of scope. FOLLOWING_AGENTS_PROTOCOL Following-Agents-Protocol: true AI-Assisted: true Assisted-by: AGENT:zai/glm-5.3-flash [maki]
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
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.
Close ISSUE-LOCAL-01M5ZEVF7HQ8SFK9F8A9WSREEP and record the row outcome
The CI fix landed as f484c76 (PR #3515, merged 2026-10-28T11:05Z), so
the row's record is now stale in one way: the issue is open and the spec
carries no outcome. This closes the issue with the dated resolution
evidence and adds the spec's ## Outcome.
The resolution records what the tree falsified: the first hypothesis
(shared-runner disk pressure on /) was rejected by evidence from its own
fix -- run 40586147690, job 122477980562, freed / to 113 GiB and still
failed 49+2 strix tests, because the worker's headroom() measures the
/tmp filesystems (worker.py:226,256), not /; the root cause is the
ubuntu-26.04 image's /tmp tmpfs (actions/runner-images#14777), which
makes the worker's 20 GiB floor unmeetable by construction. The verified
green is run 40637909804, where agent-record and build-test-vulkan
passed with df -h / /tmp showing /tmp on /dev/root at 88 GiB free.
The spec's ## Outcome records the rejected hypothesis, the six-lane
default and why the other lanes are out of scope, why the agent-record
reclamation step stays, and why the worker's 20 GiB floor is untouched.
Record-only change: the code it describes landed in the previous pull
request; this one exists because the issue close and outcome belong to
the record, and the record edit that was not in the landed change rides
alone.
FOLLOWING_AGENTS_PROTOCOL
Following-Agents-Protocol: true
AI-Assisted: true
Assisted-by: AGENT:zai/glm-5.3-flash [maki]