succeeded bazel test //src/google/protobuf/io:all //src/google/protobuf/stubs:all
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 109ms
- Evaluate target patterns 7ms
- Load, analyze dependencies and build artifacts 2m 09s
- Complete build 0ms
10720 events on 31 threads · wall 2m 09s · critical path 54.8s
Action time by phase
- local execution 309× 12m 27s
- upload inputs 491× 21.4s
- cache check 269× 3.6s
- download outputs 76× 2.1s
- outputs 465× 388ms
Summed across threads: cache checks, input uploads, queueing, remote and local execution, output downloads.
Time by category
| general information | 8227× | 33m 57s |
| action processing | 564× | 12m 45s |
| action count (local) | 309× | 12m 31s |
| skyframe evaluator | 3× | 2m 09s |
| critical path component | 12× | 54.8s |
| Unknown event | 282× | 25.0s |
| Remote execution upload time | 278× | 20.8s |
| remote action cache check | 269× | 3.6s |
| Starlark user function call | 6× | 1.4s |
| Starlark thread context | 3× | 1.2s |
Action time by mnemonic
| CppCompile | 263× | 12m 12s |
| TestRunner | 4× | 17.7s |
| CppLink | 85× | 10.1s |
| GenProto | 2× | 3.7s |
| CppArchive | 7× | 1.3s |
| Symlink | 104× | 187ms |
| SymlinkTree | 5× | 137ms |
| SolibSymlink | 83× | 113ms |
| SourceSymlinkManifest | 5× | 21ms |
| RepoMappingManifest | 5× | 13ms |
Critical path
- action 'Symlinking virtual headers for //src/google/protobuf/compiler/cpp:cpp [for tool]' 19ms
- action 'Compiling src/google/protobuf/compiler/cpp/message.cc [for tool]' 19.2s
- action 'Linking src/google/protobuf/compiler/cpp/protoc-gen-cpp [for tool]' 226ms
- runfiles for //src/google/protobuf/compiler/cpp:protoc-gen-cpp 0ms
- action 'Generating proto_library //src/google/protobuf:test_protos' 3.4s
- action 'Symlinking virtual headers for //src/google/protobuf:test_protos' 1ms
- action 'Compiling src/google/protobuf/_virtual_imports/test_protos/google/protobuf/edition_unittest.pb.cc' 18.5s
- action 'Linking src/google/protobuf/libtest_protos.so' 45ms
- action 'SolibSymlink _solib_k8/libsrc_Sgoogle_Sprotobuf_Slibtest_Uprotos.so' 1ms
- action 'Linking src/google/protobuf/io/io_test' 49ms
- runfiles for //src/google/protobuf/io:io_test 0ms
- action 'Testing //src/google/protobuf/io:io_test' 13.5s
Longest events
| buildTargets | general information | Main Thread | 2m 09s |
| runAnalysisAndExecutionPhase | general information | Main Thread | 2m 09s |
| skyframeExecutor.evaluateBuildDriverKeys | general information | Main Thread | 2m 09s |
| ParallelEvaluator.eval | general information | Main Thread | 2m 09s |
| Parallel Evaluator evaluation | skyframe evaluator | Main Thread | 2m 09s |
| action 'Compiling src/google/protobuf/compiler/cpp/message.cc [for tool]' | critical path component | Critical Path | 19.2s |
| Compiling src/google/protobuf/compiler/cpp/message.cc [for tool] | action processing | skyframe-evaluator-execution-7 | 19.2s |
| Action.execute | general information | skyframe-evaluator-execution-7 | 19.2s |
| Resources acquired | action count (local) | skyframe-evaluator-execution-7 | 19.2s |
| subprocess.run | general information | skyframe-evaluator-execution-7 | 19.1s |
| action 'Compiling src/google/protobuf/_virtual_imports/test_protos/google/protobuf/edition_unittest.pb.cc' | critical path component | Critical Path | 18.5s |
| Compiling src/google/protobuf/_virtual_imports/test_protos/google/protobuf/edition_unittest.pb.cc | action processing | skyframe-evaluator-execution-6 | 18.5s |
| Action.execute | general information | skyframe-evaluator-execution-6 | 18.4s |
| Resources acquired | action count (local) | skyframe-evaluator-execution-6 | 18.3s |
| subprocess.run | general information | skyframe-evaluator-execution-6 | 18.3s |
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.