Default / 14ab7931-7b02-44ec-9b70-fd77dbc8b056

succeeded bazel build //buildifier:buildifier //buildozer:buildozer

root@ip-172-31-43-243.ec2.internal /work/src Bazel 9.2.0 started yesterday

branch=main ci=true commit=8b07e7c mode=local run=1 team=trial user.project=buildtools wave=w1 workload=leaf

Duration

212ms

Targets

Tests

—

Actions

Cache hits

Critical path

1ms

Execution log

—

Critical path only

Scroll to zoom at the cursor, drag to pan, shift+drag (or drag in the axis) to zoom to a range, drag the overview to move. Click an event for its details and action breakdown, double-click to zoom to it, click a thread name to collapse it. Keys: +/- zoom, ←/→ pan, 0 reset, / search, c critical path, Esc clear.

Phases

Launch Blaze 9ms
Initialize command 110ms
Evaluate target patterns 6ms
Load, analyze dependencies and build artifacts 86ms
Complete build 0ms

297 events on 3 threads · wall 211ms · critical path 2ms

Action time by phase

outputs 1× 0ms

Summed across threads: cache checks, input uploads, queueing, remote and local execution, output downloads.

Time by category

general information	289×	658ms
skyframe evaluator	1×	37ms
build phase marker	1×	9ms
bazel module processing	3×	4ms
critical path component	1×	2ms
action processing	1×	2ms
complete action execution	1×	0ms

Action time by mnemonic

BazelWorkspaceStatusAction

1×

2ms

Critical path

action 'BazelWorkspaceStatusAction stable-status.txt' 2ms

Longest events

handleDiffs	general information	Main Thread	97ms
buildTargets	general information	Main Thread	93ms
handleDiffsWithMissingDiffInformation	general information	Main Thread	90ms
fsvc.getDirtyKeys	general information	Main Thread	90ms
runAnalysisAndExecutionPhase	general information	Main Thread	84ms
prepareForExecution	general information	Main Thread	41ms
skyframeExecutor.evaluateBuildDriverKeys	general information	Main Thread	37ms
ParallelEvaluator.eval	general information	Main Thread	37ms
Parallel Evaluator evaluation	skyframe evaluator	Main Thread	37ms
detectModifiedOutputFiles	general information	Main Thread	35ms
getDirtyActionValues/filterAndBatchActions	general information	Main Thread	18ms
getDirtyActionValues/statFiles	general information	Main Thread	17ms
Launch Blaze	build phase marker	Main Thread	9ms
createConfigurations	general information	Main Thread	4ms
preparingExecroot	general information	Main Thread	3ms

Timeline from build events (tests and reported actions)

Phases from Bazel's timing metrics, tests from their attempt timings, actions as reported (all actions with --build_event_publish_all_actions). The full per-action profile timeline arrives once the build's command.profile.gz can be fetched.