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

Commit Graph

Author	SHA1	Message	Date
Jan Tattermusch	b62edde1e3	[bazelified tests] Add more bazelified portability tests (and make them SOT for presubmit) (#34388 ) - bring parity between legacy portability_build_only linux job and bazelified RBE portability tests. - make grpc_portability_build_only job a no-op, since it's fully replaced by that bazelified tests (but keep grpc_portability on master job for now). For comparison: [legacy portability linux build only tests](https://source.cloud.google.com/results/invocations/f26f8b32-6878-43c7-9613-05f3111fa07c/targets) [bazel RBE bazelified tests](https://source.cloud.google.com/results/invocations/b656625f-b1e8-4b5c-9be0-b34ac9fcb31e/targets) (before this PR).	1 year ago
Jan Tattermusch	a3b4c797a7	[bazelified tests] Reenable runtests_php_linux_dbg after #34257 (#34266 ) The valgrind based test (removed in https://github.com/grpc/grpc/pull/34257) was the reason why the dbg test was disabled in the past.	1 year ago
Eugene Ostroukhov	58f1c74383	[test] Update NDK image with newer CMake (#34341 ) 1. Switch to CMake 1.18. 2. Make ergonomic change to push_testing_images.sh to allow building just a single image. 3. Update packages to reduce a number of vulnerabilities reported.	1 year ago
apolcyn	fb635a1959	[ruby] drop ruby 2.6 support (#34198 ) As title	1 year ago
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
Jan Tattermusch	422d7adf47	[bazelified tests] Reenable gcc_12 bazelified portability test (#34078 ) Needs https://github.com/grpc/grpc/pull/34035 to be merged first. With newer ccache in available in the gcc12 test image, the build is now faster so we can reenable the test.	1 year ago
Jan Tattermusch	e756a09e92	[bazel] enable more bazelified C++ distribtests (#34031 ) Reenable the bazelified version of `cpp_distribtest_cmake_linux` and `cpp_distribtest_cmake_pkgconfig_linux` distribtests	1 year ago
Jan Tattermusch	a526a091ae	[docker images] Consolidate git directory ownership workaround and upgrade ccache (#34035 ) Based on https://github.com/grpc/grpc/pull/34033 Bunch of cleanup and rebuilding many docker images from scratch - consolidate the workaround for "dubious ownership" issue reported by git. Other team members have run into this recently and used similar but not identical workarounds so some cleanup is due. - rebuilding many images increases the chance that we fix the "dubious ownership" git issue early on rather than later on in the one-at-a-time fashion in the future (and the former will prevent many teammembers from wasting time on this weird issue). - Newer version of ccache is needed for some portability tests to be able to benefit from caching (e.g. the GCC 12 portability test to get benefits of local disk caching) - this is a prerequisite for reenabling the bazelified gcc12 portability test. - upgrade node interop images to debian:11 (since debian jessie is long past EOL).	1 year ago
Jan Tattermusch	4c3ff07dac	[bazel] Reintroduce bazelified ruby and python tests (#34033 ) Reintroduce https://github.com/grpc/grpc/pull/33959. I added a fix for the python arm64 build (which is the reason why the change has been reverted earlier).	1 year 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
Xuan Wang	08659ad1c3	Revert "[bazel] Add bazelified run_tests.py tests for ruby and python" (#33999 ) Reverts grpc/grpc#33959	1 year ago
Jan Tattermusch	cb235a3e22	[bazel] Add bazelified run_tests.py tests for ruby and python (#33959 ) Context: https://github.com/grpc/grpc/pull/33707 Add python and ruby tests. Both required a few fixes so I wanted to add them separately from https://github.com/grpc/grpc/pull/33707 Manual run of all the tests: https://source.cloud.google.com/results/invocations/24c7b6ed-a8b3-4367-a4bf-8828919a9340	1 year ago
Jan Tattermusch	671453faa5	[bazel] Disable flaky bazelified run_tests.py tests (#33978 ) Most runs of these tests currently fail. Disabling them for now before I get a chance to investigate what's causing the failures. Example failures: https://source.cloud.google.com/results/invocations/9916fe8e-0fe1-4c33-a885-79a41e69c9fe https://source.cloud.google.com/results/invocations/9251a25c-0758-421d-84bd-12379f9cf10c	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

15 Commits (113dbf518389ecc643ec6025deaf68b6def7373e)