Conveyor
Default
All projects Default
Default / da51c02a-ddfa-4eef-9d12-6de0ed1065eb

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

root@ip-172-31-79-60.ec2.internal /work/src Bazel 9.2.0 started
branch=main ci=true commit=2d5a8e3 mode=rbe repo=abseil run=2 team=trial wave=w2 workload=leaf
Duration
243ms
Targets
171
Tests
—
Actions
1
Cache hits
0%
Critical path
2ms
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 9ms
  • Initialize command 81ms
  • Evaluate target patterns 8ms
  • Load, analyze dependencies and build artifacts 145ms
  • Complete build 0ms

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

Action time by phase

  • outputs 1× 1ms

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

Time by category

general information 294× 889ms
skyframe evaluator 1× 94ms
build phase marker 1× 9ms
bazel module processing 3× 5ms
critical path component 1× 3ms
action processing 1× 3ms
complete action execution 1× 1ms

Action time by mnemonic

BazelWorkspaceStatusAction 1× 3ms

Critical path

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

Longest events

buildTargets general information Main Thread 155ms
runAnalysisAndExecutionPhase general information Main Thread 141ms
skyframeExecutor.evaluateBuildDriverKeys general information Main Thread 96ms
ParallelEvaluator.eval general information Main Thread 95ms
Parallel Evaluator evaluation skyframe evaluator Main Thread 94ms
getAndVerifyServerCapabilities general information remote-executor-10 62ms
handleDiffs general information Main Thread 60ms
getAndVerifyServerCapabilities general information remote-executor-11 59ms
handleDiffsWithMissingDiffInformation general information Main Thread 51ms
fsvc.getDirtyKeys general information Main Thread 50ms
prepareForExecution general information Main Thread 35ms
detectModifiedOutputFiles general information Main Thread 29ms
getDirtyActionValues/statFiles general information Main Thread 24ms
Launch Blaze build phase marker Main Thread 9ms
createConfigurations general information Main Thread 6ms
Timeline from build events (tests and reported actions)
0ms 61ms 122ms 182ms 243ms analysis analysis · 84ms execution execution · 82ms

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.