[bazel] Log CI disk state around invocations#5657
Draft
maru-ava wants to merge 1 commit into
Draft
Conversation
maru-ava
force-pushed
the
maru/bazel-log-disk-state
branch
from
a535969 to
3dcae60
Compare
Recent Bazel CI failures have included occasional ENOSPC errors, but current runner snapshots suggest Bazel often starts with substantial free space. Before re-introducing invasive mitigations like runner pruning, add logging to show where Bazel state lives, what filesystem backs it, and how much space is available there. This updates the Bazel CI command wrapper to log: - filesystem and inode usage before and after Bazel commands - Bazel output and cache paths and the mounts backing them - per-path size summaries for Bazel output and cache directories On failure, it also logs the largest entries under the main Bazel output, cache, workspace, runner work, and temporary-directory roots to make future ENOSPC flakes easier to diagnose. Change-Id: I17056a03a1e5af8ed19a8877fe4a93a550590b83
maru-ava
force-pushed
the
maru/bazel-log-disk-state
branch
from
3dcae60 to
115ec05
Compare
maru-ava
changed the title
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
1 participant
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.
Why this should be merged
Recent Bazel CI failures have included occasional ENOSPC errors, but current runner snapshots suggest Bazel often starts with substantial free space. Before re-introducing invasive mitigations like runner pruning, add logging to show where Bazel state lives, what filesystem backs it, and how much space is available there.
This updates the Bazel CI command wrapper to log:
On failure, it also logs the largest entries under the main Bazel output, cache, workspace, runner work, and temporary-directory roots to make future ENOSPC flakes easier to diagnose.
How this was tested