Chiebot-Mirror/grpc - grpc - Gitea: Git with a cup of tea

53611 Commits

279 Branches

380 Tags

1.3 GiB

Tag: Branch: Tree: 3e24027820

Commit Graph

Author	SHA1	Message	Date
Jan Tattermusch	fdf3f5a36b	[bazelified tests] Shard bazelified bazel distribtests to make them faster (#34102 ) Basically run each of the subtests (buildtest, distribtest_cpp, distribtest_python) as a separate bazel target. - currently the bazel distribtest are the slowest targets in grpc_bazel_rbe_nonbazel - the shards are basically independent tests anyway - when split into multiple targets, they each get a separate target log so it's easier debug issues since there isn't multiple bazel invocations in each log.	1 year ago
Jan Tattermusch	d3548a3941	[bazel] Upgrade bazel repo-wide to 6.3.2 (#34088 ) - Upgrade bazel - Reduce the number of places where bazel version needs to be upgraded in future. - also make sure the list of bazel versions to test by bazelified tests is loaded from supported_versions.txt (it was hardcoded before). - ~~Try upgrading windows RBE build to bazel 6.3.2 as well.~~ The core idea: - the source of truth for supported bazel versions is in `bazel/supported_versions.txt` - the first version listed in `bazel/supported_versions.txt` is considered to be the "primary" bazel version and is going to be used in most places thoroughout the repo. - use templates to include the primary bazel version in testing dockerfiles and in a newly introduced `.bazelversion` files (which gets loaded by our existing `tools/bazel` wrapper). ~~Supersedes https://github.com/grpc/grpc/pull/33880~~	1 year ago

Author

SHA1

Message

Date

Jan Tattermusch

fdf3f5a36b

[bazelified tests] Shard bazelified bazel distribtests to make them faster (#34102 )

Basically run each of the subtests (buildtest, distribtest_cpp,
distribtest_python) as a separate bazel target.

- currently the bazel distribtest are the slowest targets in
grpc_bazel_rbe_nonbazel
- the shards are basically independent tests anyway
- when split into multiple targets, they each get a separate target log
so it's easier debug issues since there isn't multiple bazel invocations
in each log.

1 year ago

Jan Tattermusch

d3548a3941

[bazel] Upgrade bazel repo-wide to 6.3.2 (#34088 )

- Upgrade bazel
- Reduce the number of places where bazel version needs to be upgraded
in future.
- also make sure the list of bazel versions to test by bazelified tests
is loaded from supported_versions.txt (it was hardcoded before).
- ~~Try upgrading windows RBE build to bazel 6.3.2 as well.~~

The core idea:
- the source of truth for supported bazel versions is in
`bazel/supported_versions.txt`
- the first version listed in `bazel/supported_versions.txt` is
considered to be the "primary" bazel version and is going to be used in
most places thoroughout the repo.
- use templates to include the primary bazel version in testing
dockerfiles and in a newly introduced `.bazelversion` files (which gets
loaded by our existing `tools/bazel` wrapper).


~~Supersedes https://github.com/grpc/grpc/pull/33880~~

1 year ago

2 Commits (3e240278204e2fb75c8ffae858f1835b4ebee478)