| commit | e016b4f6aa65721a744c5bdefcaf5b7906c94153 | [log] [tgz] |
|---|---|---|
| author | Googler <wilwell@google.com> | Thu Jun 15 02:35:06 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Jun 15 02:36:19 2023 -0700 |
| tree | aa77ae26fa9e8dfafaae5e150e2d39c40f51a423 | |
| parent | 5dc1293a7b0bb463a81a6d3850e32ef7866a4c41 [diff] |
Set number of test on eviction to max possible value. Before that change if we have more than 3 workers per mnemonic then on every eviction we process 3 worker until the iterator is exhausted and then starting again. On every `WorkerLifecycleManager` test we run `workerPool.evict()` twice, the first to collect idle workers and the second to really evict workers. So if we have 4 worker per worker key than in first iteration we will check first 3 workers and on second iteration check 1 last worker and don't evict anything. PiperOrigin-RevId: 540517544 Change-Id: I3198eed288e1f85ac57f9232e667d87cdf22bb90
{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:
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
