tree 98694d4bfe4e51d109bcfafc6b4a9036fe998b2a
parent 4fee7efb85ce04947273e407a37eb2fdadd3a5aa
author Philipp Schrader <philipp.schrader@gmail.com> 1704582395 -0800
committer GitHub <noreply@github.com> 1704582395 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJlmd0KCRBK7hj4Ov3rIwAAhAAIAD6NReChL5edeIRgRsH1HhVO
 JqeC5IiExOiBtr3h/090Oam6L1wgq+GadgSrPBNJDAW571QdRq8Po5knZ7orgS0O
 nmd50m5Ym55p9jcLdnyKiktVvS5/xIskb+L4nXXgkCt8iFm4c0Dxkpoy1x32Uhzg
 i55Jat/pk913j1/NR2UY71OZWTZhtQ41HGQKuDFAju3aAx2GnFywKHtI24wJ8+ZT
 eETLmzYM5/DSCU6adapWQc2eQZ9Iy5M588CuIzQiVsXkvnsPOzBjPz3gmIPFeFLl
 8Gu05PosL8Pn6Mlnm5Q45Ih/zeIPmXs+Q8veRg/L/mhK1FOaZC8VKs3xAXmZyww=
 =DEn+
 -----END PGP SIGNATURE-----
 

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 <rlevasseur@google.com>