Default / 3a2f6704-ba69-4599-bb84-9793a31bcf9d

running bazel build //...

root@ip-172-31-11-19.ec2.internal /work/src/cpp-tutorial/stage3 Bazel 9.2.0 started
branch=main ci=true commit=45bfd9d mode=rbe repo=cpp-tutorial run=2 team=trial wave=w3 workload=wide
Duration
Targets
1
Tests
Actions
Cache hits
Critical path
Execution log

No profile was reported. Bazel writes one by default (--profile); it appears here once it can be fetched or is uploaded.

Timeline from build events (tests and reported actions)

Nothing to draw yet: the timeline fills in as tests and actions report their timing.

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.