Default / edabf250-e73f-46d6-a39f-57e1d765ffc8

failed bazel test //...

no tests found (exit 4) root@ip-172-31-8-223.ec2.internal /work/src/cpp-tutorial/stage3 Bazel 9.2.0 started yesterday

branch=main ci=true commit=45bfd9d mode=cache repo=cpp-tutorial run=2 team=trial wave=w3 workload=test

Duration

112ms

Targets

Tests

—

Actions

Cache hits

Critical path

2ms

Execution log

—

Critical path only

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 10ms
Initialize command 66ms
Evaluate target patterns 8ms
Load, analyze dependencies and build artifacts 27ms
Complete build 0ms

303 events on 5 threads · wall 111ms · 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×	287ms
skyframe evaluator	2×	13ms
build phase marker	1×	10ms
bazel module processing	3×	4ms
critical path component	1×	3ms
action processing	1×	2ms
complete action execution	1×	1ms

Action time by mnemonic

BazelWorkspaceStatusAction

1×

2ms

Critical path

action 'BazelWorkspaceStatusAction stable-status.txt' 3ms

Longest events

getAndVerifyServerCapabilities	general information	remote-executor-1	53ms
handleDiffs	general information	Main Thread	40ms
buildTargets	general information	Main Thread	37ms
handleDiffsWithMissingDiffInformation	general information	Main Thread	36ms
fsvc.getDirtyKeys	general information	Main Thread	36ms
runAnalysisAndExecutionPhase	general information	Main Thread	24ms
skyframeExecutor.evaluateBuildDriverKeys	general information	Main Thread	11ms
ParallelEvaluator.eval	general information	Main Thread	10ms
Parallel Evaluator evaluation	skyframe evaluator	Main Thread	10ms
Launch Blaze	build phase marker	Main Thread	10ms
createConfigurations	general information	Main Thread	7ms
RemoteModule.beforeCommand	general information	Main Thread	6ms
prepareForExecution	general information	Main Thread	5ms
evaluateTargetPatterns	general information	Main Thread	4ms
ParallelEvaluator.eval	general information	Main Thread	3ms

Timeline from build events (tests and reported actions)

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.