Default / bc3109dd-43b7-4f77-84bb-e2cb09e66b3f

succeeded bazel build //absl/strings/... //absl/container/...

root@ip-172-31-64-13.ec2.internal /work/src Bazel 9.2.0 started
branch=main ci=true commit=2d5a8e3 mode=rbe repo=abseil run=1 team=trial wave=w2 workload=leaf
Duration
229ms
Targets
171
Tests
Actions
1
Cache hits
0%
Critical path
3ms
Execution log

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 82ms
  • Evaluate target patterns 6ms
  • Load, analyze dependencies and build artifacts 132ms
  • Complete build 0ms

302 events on 6 threads · wall 229ms · critical path 3ms

Action time by phase

  • outputs 1ms

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

Time by category

general information 294× 831ms
skyframe evaluator 87ms
build phase marker 8ms
bazel module processing 7ms
critical path component 3ms
action processing 3ms
complete action execution 1ms

Action time by mnemonic

BazelWorkspaceStatusAction 3ms

Critical path

  1. action 'BazelWorkspaceStatusAction stable-status.txt' 3ms

Longest events

buildTargets general information Main Thread 140ms
runAnalysisAndExecutionPhase general information Main Thread 129ms
skyframeExecutor.evaluateBuildDriverKeys general information Main Thread 88ms
ParallelEvaluator.eval general information Main Thread 88ms
Parallel Evaluator evaluation skyframe evaluator Main Thread 87ms
handleDiffs general information Main Thread 60ms
getAndVerifyServerCapabilities general information remote-executor-11 58ms
getAndVerifyServerCapabilities general information remote-executor-9 58ms
handleDiffsWithMissingDiffInformation general information Main Thread 50ms
fsvc.getDirtyKeys general information Main Thread 49ms
prepareForExecution general information Main Thread 31ms
detectModifiedOutputFiles general information Main Thread 27ms
getDirtyActionValues/statFiles general information Main Thread 22ms
Launch Blaze build phase marker Main Thread 8ms
createConfigurations general information Main Thread 7ms
Timeline from build events (tests and reported actions)
0ms 57ms 115ms 172ms 229ms analysis analysis · 69ms execution execution · 78ms

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.