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

53565 Commits

276 Branches

377 Tags

1.2 GiB

Tag: Branch: Tree: c8f467aea9

Commit Graph

Author SHA1 Message Date

Author	SHA1	Message	Date
Esun Kim	3bd6c38650	[Infra] Use Bazel 6 and drop Bazel 4 (Part 2) (#32910 ) Oops I missed important changes from https://github.com/grpc/grpc/pull/32712. And it turned out that there are two problems that I couldn't fix at this point. - Windows Bazel RBE Linker Error: This may be caused by how new Bazel 6 invokes build tools chain but it's not clear. I put workaround to use Bazel 5 by using `OVERRIDE_BAZEL_VERSION=5.4.1` - Rule `rules_pods` to fetch CronetFramework from CocoaPod has incompatibility with sort of built-in apple toolchain. (https://github.com/bazel-xcode/PodToBUILD/issues/232): I couldn't find a workaround to fix this so I ended up disabling all tests depending this target.	2 years ago
Jan Tattermusch	631392f2e7	Upgrade bazel version to bazel 5.3 (repo-wide) (#30844 ) * update bazel to 5.3.0 * regenerate dockerfiles * update bazel distribtest * update docker image templates * regenerate dockerfiles 2 * regenerate bazel_support.md * upgrade rules_apple and apple_support bazel deps * Revert "upgrade rules_apple and apple_support bazel deps" This reverts commit `eb9a0d2155`. * fix objc bazel 5.3 build on kokoro mojave image	2 years ago
Jan Tattermusch	6d3c45ff7b	Add dockerized ARM64 tests (bazel C/C++, C#, PHP, ruby, python) (#28966 ) * C# arm64 docker image * add ruby arm64 docker image * add bazel_arm64 docker image * add python arm64 image * add php arm64 docker image * regenerate * add support for running arm64 tests with run_tests.py * restrict arm64 testing to python3.9 * first version of bazel arm64 C++ tests * add arm64 job configs * add initial checks to push_testing_images.sh	3 years ago

Esun Kim

3bd6c38650

[Infra] Use Bazel 6 and drop Bazel 4 (Part 2) (#32910 )

Oops I missed important changes from
https://github.com/grpc/grpc/pull/32712. And it turned out that there
are two problems that I couldn't fix at this point.
- Windows Bazel RBE Linker Error: This may be caused by how new Bazel 6
invokes build tools chain but it's not clear. I put workaround to use
Bazel 5 by using `OVERRIDE_BAZEL_VERSION=5.4.1`
- Rule `rules_pods` to fetch CronetFramework from CocoaPod has
incompatibility with sort of built-in apple toolchain.
(https://github.com/bazel-xcode/PodToBUILD/issues/232): I couldn't find
a workaround to fix this so I ended up disabling all tests depending
this target.

2 years ago

Jan Tattermusch

631392f2e7

Upgrade bazel version to bazel 5.3 (repo-wide) (#30844 )

* update bazel to 5.3.0

* regenerate dockerfiles

* update bazel distribtest

* update docker image templates

* regenerate dockerfiles 2

* regenerate bazel_support.md

* upgrade rules_apple and apple_support bazel deps

* Revert "upgrade rules_apple and apple_support bazel deps"

This reverts commit eb9a0d2155.

* fix objc bazel 5.3 build on kokoro mojave image

2 years ago

Jan Tattermusch

6d3c45ff7b

Add dockerized ARM64 tests (bazel C/C++, C#, PHP, ruby, python) (#28966 )

* C# arm64 docker image

* add ruby arm64 docker image

* add bazel_arm64 docker image

* add python arm64 image

* add php arm64 docker image

* regenerate

* add support for running arm64 tests with run_tests.py

* restrict arm64 testing to python3.9

* first version of bazel arm64 C++ tests

* add arm64 job configs

* add initial checks to push_testing_images.sh

3 years ago

3 Commits (c8f467aea99e074776901fc4c53d59565b90d988)