Repository navigation
chore: benchmark OpenClaw 167459 with 32 GiB disk - #73
Open
bb-flightcontrol[bot] wants to merge 1 commit into
Open
bb-flightcontrol[bot] wants to merge 1 commit into
bb-flightcontrol[bot] wants to merge 1 commit into
Conversation
|
This PR does not match any of the 1 configured review trigger rule. |
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.
What Problem This Solves
Benchmark only; do not merge. Exact-source replay of OpenClaw sample 167459.
User Impact
No product change; benchmark only.
All ten systemd-dependent job definitions and their failure monitor are removed; no hosted fallback. Warmers and all non-CI workflows are disabled. Unique labels include run, attempt, job and matrix identity.
Why This Change Was Made
After PR #46 exposed the new 8 GiB per-step write limit, all sandbox labels now reserve 32 GiB. CPU, memory, source, retained job bodies and cache policy are unchanged. That failed attempt remains separate in the evidence.
Evidence
Generated using each source revision's pinned formatter. Source trees and changed paths validated locally and at publication. Fresh attempt-1 run on released runner 1.1.101; setup, queue, execution, cache, placement, version and benchmark-window API cost will be collected separately. Upstream timings are historical, not a simultaneous three-provider test.
Written by Devin