Default / 64e611dd-4e4c-4e6c-ab55-203816d71515

succeeded bazel build //...

root@ip-172-31-71-169.ec2.internal /work/src/test/fixtures/workspace Bazel 9.2.0 started yesterday

branch=main ci=true commit=e697fab mode=local run=1 team=trial user.project=fixture wave=w1 workload=leaf

Duration

124ms

Targets

Tests

—

Actions

Cache hits

Critical path

4ms

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 67ms
Evaluate target patterns 8ms
Load, analyze dependencies and build artifacts 39ms
Complete build 0ms

312 events on 4 threads · wall 124ms · critical path 4ms

Action time by phase

outputs 3× 1ms

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

Time by category

general information	300×	291ms
skyframe evaluator	1×	14ms
build phase marker	1×	9ms
bazel module processing	3×	8ms
action processing	3×	5ms
critical path component	1×	4ms
complete action execution	3×	1ms

Action time by mnemonic

BazelWorkspaceStatusAction	1×	4ms
ExecutableSymlink	1×	1ms
RunfilesTree	1×	0ms

Critical path

action 'BazelWorkspaceStatusAction stable-status.txt' 4ms

Longest events

buildTargets	general information	Main Thread	50ms
handleDiffs	general information	Main Thread	44ms
handleDiffsWithMissingDiffInformation	general information	Main Thread	42ms
fsvc.getDirtyKeys	general information	Main Thread	41ms
runAnalysisAndExecutionPhase	general information	Main Thread	37ms
skyframeExecutor.evaluateBuildDriverKeys	general information	Main Thread	14ms
ParallelEvaluator.eval	general information	Main Thread	14ms
Parallel Evaluator evaluation	skyframe evaluator	Main Thread	14ms
prepareForExecution	general information	Main Thread	12ms
Launch Blaze	build phase marker	Main Thread	9ms
createConfigurations	general information	Main Thread	8ms
detectModifiedOutputFiles	general information	Main Thread	6ms
reparse options with main repo mapping	bazel module processing	Main Thread	6ms
action 'BazelWorkspaceStatusAction stable-status.txt'	critical path component	Critical Path	4ms
BazelWorkspaceStatusAction stable-status.txt	action processing	skyframe-evaluator-execution-0	4ms

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.