You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chore: Migrate to rules_bazel_integration_test (#1598)
This patch deletes the old copy of `bazel_integration_test` that we
had vendored into the repo. It's replaced with the maintained
`rules_bazel_integration_test`.
Summary of changes:
* Increases minimum tested bazel version to 6.4.0.
rules_bazel_integration_test depends on some features in 6.4
* Moves several CI jobs to be BIT tests. This free ups
about 10 CI slots.
* Runs these tests under a separate CI job. This is so that feedback
from the regular test jobs is faster.
Notes about these bazel-in-bazel integration tests:
* The tests are very heavy and easily overwhelm a system. Unfortunately,
there doesn't appear to be a way to cap their parallelism; only
disable it entirely using the `exclusive` tag. Some light
testing shows there is some speedup to be gained on CI
if we can, in the future, limit them to 2 or 4 concurrent
executions.
* A special version named "self" is created that re-uses
whatever the outer Bazel program is. This is mainly so that
Bazel's "at head" testing pipelines (the one that runs tests
with Bazel built from head) are able to affect the integration tests.
It also comes in handy when locally testing a custom Bazel build.
* The globbing of child workspace files can be somewhat prone to
following `bazel-*` symlinks, so its important the `.bazelignore`
and deleted packages configs are up-to-date. Otherwise the
globbing can turn into 30,000+ files and consume a system-freezing
level of memory and CPU.
Fixes#1209
---------
Co-authored-by: Richard Levasseur <[email protected]>
0 commit comments