Default / f89d63fd-b7bd-456c-953c-be46201f4088

succeeded bazel test //app:pass_test //app:sharded_test //app:uses_greeting_test

root@ip-172-31-32-20.ec2.internal /work/src/test/fixtures/workspace Bazel 9.2.0 started
branch=main ci=true commit=e697fab mode=cache run=1 team=trial user.project=fixture wave=w1 workload=test
Duration
286ms
Targets
3
Tests
3
Actions
6
Cache hits
150%
Critical path
157ms
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 11ms
  • Initialize command 74ms
  • Evaluate target patterns 8ms
  • Load, analyze dependencies and build artifacts 192ms
  • Complete build 0ms

423 events on 12 threads · wall 286ms · critical path 158ms

Action time by phase

  • download outputs 14× 488ms
  • cache check 10× 56ms
  • outputs 31ms
  • local execution 28ms
  • upload inputs 9ms

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

Time by category

general information 388× 1.9s
action processing 588ms
remote output download 233ms
skyframe evaluator 176ms
critical path component 158ms
remote action cache check 10× 56ms
action count (local) 32ms
complete action execution 31ms
build phase marker 11ms
bazel module processing 5ms

Action time by mnemonic

TestRunner 585ms
BazelWorkspaceStatusAction 3ms

Critical path

  1. action 'Testing //app:uses_greeting_test' 158ms

Longest events

buildTargets general information Main Thread 203ms
runAnalysisAndExecutionPhase general information Main Thread 190ms
skyframeExecutor.evaluateBuildDriverKeys general information Main Thread 173ms
ParallelEvaluator.eval general information Main Thread 173ms
Parallel Evaluator evaluation skyframe evaluator Main Thread 173ms
action 'Testing //app:uses_greeting_test' critical path component Critical Path 158ms
Testing //app:uses_greeting_test action processing skyframe-evaluator-execution-3 157ms
Action.execute general information skyframe-evaluator-execution-3 153ms
Testing //app:sharded_test (shard 2 of 3) action processing skyframe-evaluator-execution-6 108ms
Testing //app:sharded_test (shard 3 of 3) action processing skyframe-evaluator-execution-5 107ms
Testing //app:pass_test action processing skyframe-evaluator-execution-2 107ms
Testing //app:sharded_test (shard 1 of 3) action processing skyframe-evaluator-execution-7 106ms
Action.execute general information skyframe-evaluator-execution-2 98ms
Action.execute general information skyframe-evaluator-execution-5 98ms
Action.execute general information skyframe-evaluator-execution-7 98ms
Timeline from build events (tests and reported actions)
0ms 72ms 143ms 215ms 286ms analysis analysis · 6ms execution execution · 171ms //app:sharded_test s2/a1 //app:sharded_test s2/a1 · PASSED · 535ms //app:uses_greeting_test //app:uses_greeting_test · PASSED · 21ms //app:pass_test //app:pass_test · PASSED · 531ms //app:sharded_test //app:sharded_test · PASSED · 544ms //app:sharded_test s3/a1 //app:sharded_test s3/a1 · PASSED · 527ms

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.