Default / ab9997b5-87a3-47bd-9226-c0ec57dc27aa

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

root@ip-172-31-15-211.ec2.internal /work/src Bazel 9.2.0 started
branch=main ci=true commit=2d5a8e3 mode=local run=1 team=trial user.project=abseil wave=w1 workload=leaf
Duration
213ms
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 73ms
  • Evaluate target patterns 6ms
  • Load, analyze dependencies and build artifacts 125ms
  • Complete build 0ms

298 events on 3 threads · wall 213ms · critical path 2ms

Action time by phase

  • outputs 0ms

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

Time by category

general information 290× 674ms
skyframe evaluator 72ms
build phase marker 9ms
bazel module processing 6ms
critical path component 2ms
action processing 2ms
complete action execution 0ms

Action time by mnemonic

BazelWorkspaceStatusAction 2ms

Critical path

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

Longest events

buildTargets general information Main Thread 132ms
runAnalysisAndExecutionPhase general information Main Thread 122ms
skyframeExecutor.evaluateBuildDriverKeys general information Main Thread 73ms
ParallelEvaluator.eval general information Main Thread 72ms
Parallel Evaluator evaluation skyframe evaluator Main Thread 72ms
handleDiffs general information Main Thread 53ms
handleDiffsWithMissingDiffInformation general information Main Thread 43ms
fsvc.getDirtyKeys general information Main Thread 43ms
prepareForExecution general information Main Thread 42ms
detectModifiedOutputFiles general information Main Thread 37ms
getDirtyActionValues/statFiles general information Main Thread 31ms
Launch Blaze build phase marker Main Thread 9ms
getDirtyActionValues/filterAndBatchActions general information Main Thread 6ms
createConfigurations general information Main Thread 5ms
reparse options with main repo mapping bazel module processing Main Thread 4ms
Timeline from build events (tests and reported actions)
0ms 53ms 107ms 160ms 213ms analysis analysis · 55ms execution execution · 54ms

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.