Default / 65e626f9-f031-4284-b607-04ac871551f2

succeeded bazel build //...

root@ip-172-31-67-50.ec2.internal /work/src/test/fixtures/workspace Bazel 9.2.0 started 4d ago

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

Duration

102ms

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

313 events on 5 threads · wall 102ms · 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×	234ms
build phase marker	1×	12ms
skyframe evaluator	1×	12ms
bazel module processing	3×	5ms
action processing	3×	3ms
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	39ms
handleDiffs	general information	Main Thread	36ms
handleDiffsWithMissingDiffInformation	general information	Main Thread	34ms
fsvc.getDirtyKeys	general information	Main Thread	34ms
runAnalysisAndExecutionPhase	general information	Main Thread	29ms
skyframeExecutor.evaluateBuildDriverKeys	general information	Main Thread	12ms
Launch Blaze	build phase marker	Main Thread	12ms
ParallelEvaluator.eval	general information	Main Thread	12ms
Parallel Evaluator evaluation	skyframe evaluator	Main Thread	12ms
prepareForExecution	general information	Main Thread	9ms
detectModifiedOutputFiles	general information	Main Thread	5ms
createConfigurations	general information	Main Thread	5ms
reparse options with main repo mapping	bazel module processing	Main Thread	3ms
getDirtyActionValues/statFiles	general information	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.