Default / 1cddbc98-8bb5-4916-9789-3851ca5314da

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

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

515 events on 31 threads · wall 2.1s · critical path 2.0s

Action time by phase

  • remote execution 20× 6.6s
  • upload inputs 23× 2.1s
  • download outputs 15× 355ms
  • setup 311ms
  • cache check 10× 101ms
  • outputs 12ms

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

Time by category

general information 431× 18.8s
action processing 8.5s
remote action execution 20× 6.6s
Remote execution file fetching 10× 3.3s
Remote execution process wall time 2.1s
skyframe evaluator 2.0s
critical path component 2.0s
Remote execution upload time 10× 1.5s
Remote execution setup 311ms
remote output download 202ms

Action time by mnemonic

TestRunner 8.5s
BazelWorkspaceStatusAction 2ms

Critical path

  1. action 'Testing //app:sharded_test (shard 3 of 3)' 2.0s

Longest events

buildTargets general information Main Thread 2.1s
runAnalysisAndExecutionPhase general information Main Thread 2.0s
skyframeExecutor.evaluateBuildDriverKeys general information Main Thread 2.0s
ParallelEvaluator.eval general information Main Thread 2.0s
Parallel Evaluator evaluation skyframe evaluator Main Thread 2.0s
action 'Testing //app:sharded_test (shard 3 of 3)' critical path component Critical Path 2.0s
Testing //app:sharded_test (shard 3 of 3) action processing skyframe-evaluator-execution-8 2.0s
Action.execute general information skyframe-evaluator-execution-8 2.0s
Testing //app:sharded_test (shard 1 of 3) action processing skyframe-evaluator-execution-1 1.8s
Action.execute general information skyframe-evaluator-execution-1 1.7s
Testing //app:sharded_test (shard 2 of 3) action processing skyframe-evaluator-execution-3 1.7s
Action.execute general information skyframe-evaluator-execution-3 1.7s
Testing //app:pass_test action processing skyframe-evaluator-execution-0 1.7s
Action.execute general information skyframe-evaluator-execution-0 1.7s
Testing //app:uses_greeting_test action processing skyframe-evaluator-execution-2 1.3s
Timeline from build events (tests and reported actions)
0ms 534ms 1.1s 1.6s 2.1s analysis analysis · 7ms execution execution · 2.0s //app:pass_test //app:pass_test · PASSED · 516ms //app:uses_greeting_test //app:uses_greeting_test · PASSED · 15ms //app:sharded_test //app:sharded_test · PASSED · 518ms //app:sharded_test s2/a1 //app:sharded_test s2/a1 · PASSED · 521ms //app:sharded_test s3/a1 //app:sharded_test s3/a1 · PASSED · 518ms

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.