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

Commit Graph

Author	SHA1	Message	Date
AJ Heller	0c58f1551c	[build] Speed up the strict_build CI job (#34841 ) The `bazel_build_with_strict_warnings_linux` job was taking nearly an hour to complete. This change brings it down to ~20m by splitting up the build targets into 7 separate RBE actions. --------- Co-authored-by: drfloob <drfloob@users.noreply.github.com>	1 year ago
Esun Kim	10e08e06bd	[Test] Bump the timeout for bazelify distribtest_php_linux_x64_debian10 (#34600 ) Bump the timeout as distribtest_php_linux_x64_debian10 takes longer while building core.	1 year ago
Jan Tattermusch	3b40af376e	[bazelified tests] First attempt at bazelified rules for building artifacts/packages (#34462 ) Foundation for being able to bazelify the build artifact -> build package -> distribtest workflow tests. Main ideas: - "build artifact" and "build packages" will be represented by a custom genrule (that runs the build on RBE under a docker container). - since genrule doesn't support displaying logs for each target as a separate "target log" (in the same way that bazel tests do), and we generally want readable per-target logs for the bazelified test, a pair of targets will be created for each "build artifact task": - a genrule that actually performs the build, creates an archive with artifacts and stores the exitcode and build log as rule outputs - a corresponding "build_test" sh_test that simply looks at the result of the genrule and presents the build log and build result a "target log" for this test.	1 year ago
Jan Tattermusch	60f25c289b	[bazelified tests] Bazelify tests from "linux/grpc_bazel_build" and make the original test job a noop. (#34429 ) Bazelify tests from "linux/grpc_bazel_build" kokoro job by creating 3 bazelified tests - "build with strict warning", "build with no_xds=True" and "build with no_xds=True negative test". - also make the original "linux/grpc_bazel_build" kokoro job a no-op (since bazelified tests now provide the same coverage).	1 year ago
Jan Tattermusch	866fc41067	[bazelified tests] Make bazelified C basictests build only (#34428 ) - make C-core basictests use `--build_only` when running as bazelified tests. This is because the volume of C core tests is expected to grow very significantly after https://github.com/grpc/grpc/pull/34419 and currently the non-bazelified counterpart of the tests (the presubmit grpc_basictests_c_cpp_build_only job) is also "build only". - make the linux presubmit job `grpc_basictests_c_cpp_build_only` a noop, since the bazelified tests already give the same coverage on presubmit.	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
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	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	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

14 Commits (73950425c9f00d56ce8d6b9f2f36f69b6dce4a40)