| commit | 83d7e1d27a84f2db0d6197af50955e26a9db04fb | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Tue Dec 03 06:47:45 2019 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Dec 03 06:48:54 2019 -0800 |
| tree | e688058ed386400fc3517d5dc68a7a4e36c9de9e | |
| parent | 949e806a4b4e24b36d6d41cc4f9721c8f5ab63ad [diff] |
A build's or test's critical path run time was surpassing the execution run time, which is impossible. The root cause was that within the same critical path, multiple actions were run in parallel. Therefore the total run time is the union of all those actions instead of the aggregate (which was the original implementation). For example, there are some cases where an action's dependency can run and complete during the time it's dependent action is in its discover inputs phase. In this scenario the total run time would be the "dependent's finish - start time" rather than: "dependent's finish - start time" + "dependency's finish - start time". The solution was to create a timeline of each component that has it's child's timeline. Since each child is requested and finished before the start of the dependent component, we can assure that the dependent calling the child's timeline returns the child's longest and finalized timeline. The timeline of type RangeSet was also used because this can keep track of any gaps in between each time range, keeping this logic consistent with the original implementation. RELNOTES: Critical path run time should not have a longer run time than total execution run time. PiperOrigin-RevId: 283535419
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
See CONTRIBUTING.md
