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

Tag: Branch: Tree: 0148b49aea

Author	SHA1	Message	Date
Esun Kim	c4682fe259	[Build] Revert "[Build] Use -msse2 option only for 32-bit Intel (#38024 )" (#38074 ) This reverts commit `574b19ec31`. <!-- If you know who should review your pull request, please assign it to that person, otherwise the pull request would get assigned randomly. If your pull request is for a specific language, please add the appropriate lang label. --> Closes #38074 PiperOrigin-RevId: 693803071	2 months ago
Esun Kim	574b19ec31	[Build] Use -msse2 option only for 32-bit Intel (#38024 ) This might not be needed? (From https://github.com/grpc/grpc/issues/37976) - Boringssl commit requiring -msse2: `56d3ad9d23 (diff-f628d148f94bbab9e22a1ad426ccd94311f1fb87bbe5cc533cb85aee18b07a20R248)` - gRPC change to add -msse2 https://github.com/grpc/grpc/pull/36089 --- Answer to the quesiton above is yes; The -msse2 option remains necessary for gRPC on i686 due to BoringSSL's requirements. However, the existing CMake condition for this option was too broad, potentially including ARM architectures where SSE2 isn't supported, leading to compilation errors. I've refined the condition to specifically target 32-bit x86 architectures. Furthermore, to ensure accurate architecture detection within our dockerized tests, I've configured x86 tests to utilize the linux32 command. This ensures that uname -a correctly reports i686, allowing gRPC's CMake to identify the architecture and apply the -msse2 option as needed. It's important to note that RBE overrides the default entrypoint, so RBE-based tests must explicitly invoke linux32 even if the Docker image already has it set. Fixes https://github.com/grpc/grpc/issues/37976 Closes #38024 PiperOrigin-RevId: 693026079	3 months ago
Jan Tattermusch	5eb227936e	[bazel] Add more bazelified tests (#34005 ) - some cleanup - add bazel distribtests (to run the existing test_single_bazel_version.sh locally under a docker container created by RBE). - add c++ distribtests - rename `grpc_run_tests_py_test` macro to `grpc_run_tests_harness_test` - as requested previously to avoid confusion with `*_py_test` rules	1 year ago
Jan Tattermusch	2b0a9d3916	[bazel] Teach bazel how to run non-bazel test suites under docker locally and on RBE (#33707 ) Add "bazelified" non-bazel tests. See tools/bazelify_tests/README.md for the core idea. - add a bunch of test targets that run under docker and execute tests that correspond to `run_tests.py -l LANG ...` - many more tests can be added in the future - to enable running some of the C/C++ portability tests easily, added support for `--cmake_extra_configure_args` in run_tests.py (the change is fairly small). Example passing build that shows how test results are structured: https://source.cloud.google.com/results/invocations/21295351-a3e3-4be1-b6e9-aaf52195a044/targets	1 year ago