Default / f5995865-103b-4263-aa0e-314900080b1c

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=wide

Duration

112ms

Targets

Tests

—

Actions

Cache hits

Critical path

2ms

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 11ms
Initialize command 60ms
Evaluate target patterns 6ms
Load, analyze dependencies and build artifacts 34ms
Complete build 0ms

313 events on 4 threads · wall 111ms · critical path 2ms

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×	260ms
skyframe evaluator	1×	14ms
build phase marker	1×	11ms
bazel module processing	3×	5ms
action processing	3×	4ms
critical path component	2×	2ms
complete action execution	3×	1ms

Action time by mnemonic

BazelWorkspaceStatusAction	1×	2ms
ExecutableSymlink	1×	1ms
RunfilesTree	1×	0ms

Critical path

action 'Creating symlink app/uses_greeting_test' 2ms
runfiles for //app:uses_greeting_test 1ms

Longest events

buildTargets	general information	Main Thread	42ms
handleDiffs	general information	Main Thread	41ms
handleDiffsWithMissingDiffInformation	general information	Main Thread	38ms
fsvc.getDirtyKeys	general information	Main Thread	38ms
runAnalysisAndExecutionPhase	general information	Main Thread	31ms
skyframeExecutor.evaluateBuildDriverKeys	general information	Main Thread	15ms
ParallelEvaluator.eval	general information	Main Thread	14ms
Parallel Evaluator evaluation	skyframe evaluator	Main Thread	14ms
Launch Blaze	build phase marker	Main Thread	11ms
prepareForExecution	general information	Main Thread	10ms
detectModifiedOutputFiles	general information	Main Thread	6ms
createConfigurations	general information	Main Thread	4ms
getDirtyActionValues/statFiles	general information	Main Thread	3ms
reparse options with main repo mapping	bazel module processing	Main Thread	3ms
compute main repo mapping	bazel module processing	Main Thread	2ms

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.