Conveyor
Default
All projects Default
Default / f3a335b1-7682-4004-91e6-310041a4e11b

succeeded bazel build //buildifier:buildifier //buildozer:buildozer

root@ip-172-31-72-73.ec2.internal /work/src Bazel 9.2.0 started
branch=main ci=true commit=8b07e7c mode=local run=1 team=trial user.project=buildtools wave=w1 workload=buildfile
Duration
180ms
Targets
2
Tests
—
Actions
1
Cache hits
0%
Critical path
1ms
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 83ms
  • Evaluate target patterns 6ms
  • Load, analyze dependencies and build artifacts 84ms
  • Complete build 0ms

298 events on 4 threads · wall 180ms · critical path 2ms

Action time by phase

  • outputs 1× 0ms

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

Time by category

general information 289× 552ms
skyframe evaluator 1× 50ms
gc notification 1× 10ms
build phase marker 1× 8ms
bazel module processing 3× 4ms
critical path component 1× 2ms
action processing 1× 1ms
complete action execution 1× 0ms

Action time by mnemonic

BazelWorkspaceStatusAction 1× 1ms

Critical path

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

Longest events

buildTargets general information Main Thread 91ms
runAnalysisAndExecutionPhase general information Main Thread 81ms
handleDiffs general information Main Thread 70ms
handleDiffsWithMissingDiffInformation general information Main Thread 69ms
fsvc.getDirtyKeys general information Main Thread 68ms
skyframeExecutor.evaluateBuildDriverKeys general information Main Thread 50ms
ParallelEvaluator.eval general information Main Thread 50ms
Parallel Evaluator evaluation skyframe evaluator Main Thread 50ms
prepareForExecution general information Main Thread 22ms
detectModifiedOutputFiles general information Main Thread 16ms
getDirtyActionValues/statFiles general information Main Thread 13ms
minor GC gc notification Garbage Collector 10ms
Launch Blaze build phase marker Main Thread 8ms
createConfigurations general information Main Thread 6ms
preparingExecroot general information Main Thread 4ms
Timeline from build events (tests and reported actions)
0ms 45ms 90ms 135ms 180ms analysis analysis · 33ms execution execution · 20ms

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.