Ensure ResourceCollector executes a final collection pass on stop. Previously, ResourceCollector abruptly exited the collection loop upon interruption without performing a collection pass for the tail time interval between the last 200 ms sleep tick and when the profiler was stopped. For fast builds, this caused metrics like Skyframe ACTION_EXECUTION counts to be omitted entirely from the JSON trace profile, leading to flaky failures in integration tests (such as profiler_test). Buildkite failure: https://buildkite.com/bazel/bazel-bazel/builds/36681#01a035ac-dc09-4093-9c89-8824e93b8452 Wrap the collection loop in a try-finally block in ResourceCollector that runs one last collectOnce pass before exiting, ensuring metrics up to the stop timestamp are fully recorded into the profile. Also guard against null SystemNetworkStatsService in LocalResourceUsageCollectors and NetworkMetricsCollector, which can be null in test environments where network services are not registered. PiperOrigin-RevId: 970500451 Change-Id: Ib6edd35fef47ddc134b9c7f152f09ff5177bddcf
{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.
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
