Default / a90f610a-8677-46c3-85f4-13498da25783

succeeded bazel build //...

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

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

Duration

104ms

Targets

Tests

—

Actions

Cache hits

Critical path

3ms

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 8ms
Initialize command 57ms
Evaluate target patterns 7ms
Load, analyze dependencies and build artifacts 32ms
Complete build 0ms

315 events on 6 threads · wall 104ms · critical path 3ms

Action time by phase

outputs 3× 2ms

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

Time by category

general information	303×	301ms
skyframe evaluator	1×	12ms
build phase marker	1×	8ms
bazel module processing	3×	6ms
action processing	3×	5ms
critical path component	1×	3ms
complete action execution	3×	2ms

Action time by mnemonic

BazelWorkspaceStatusAction	1×	3ms
ExecutableSymlink	1×	1ms
RunfilesTree	1×	1ms

Critical path

action 'BazelWorkspaceStatusAction stable-status.txt' 3ms

Longest events

getAndVerifyServerCapabilities	general information	remote-executor-3	53ms
buildTargets	general information	Main Thread	41ms
handleDiffs	general information	Main Thread	38ms
handleDiffsWithMissingDiffInformation	general information	Main Thread	37ms
fsvc.getDirtyKeys	general information	Main Thread	36ms
runAnalysisAndExecutionPhase	general information	Main Thread	30ms
skyframeExecutor.evaluateBuildDriverKeys	general information	Main Thread	13ms
ParallelEvaluator.eval	general information	Main Thread	13ms
Parallel Evaluator evaluation	skyframe evaluator	Main Thread	12ms
prepareForExecution	general information	Main Thread	8ms
Launch Blaze	build phase marker	Main Thread	8ms
createConfigurations	general information	Main Thread	6ms
reparse options with main repo mapping	bazel module processing	Main Thread	4ms
detectModifiedOutputFiles	general information	Main Thread	4ms
action 'BazelWorkspaceStatusAction stable-status.txt'	critical path component	Critical Path	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.