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

Commit Graph

Author	SHA1	Message	Date
Richard Belleville	7aa43b7a55	Create Bazel gevent test harness (#27507 ) * WIP * Add gevent test suite run under Bazel. * Fix things up * Yapf * Fix up Bazel files * Make py_grpc_test fancier * Attempt to fix Windows RBE * Attempt to kick GitHub * Fix Python 2 runs * Yet more fixes * And the patch file too * I am an idiot * Mark gevent tests flaky * Try to make rules_python more tolerant * Typo * Exclude reconnect test from gevent * Remove unnecessary parts of patch * Buildifier * You saw nothing * isort * Move py_grpc_test to an internal-only file * Review comments * More reviewer comments * Review	3 years ago
Richard Belleville	2f4360a596	Remove unintentional additions	4 years ago
Richard Belleville	849c9b01bf	Make patch work for downstream dependencies	4 years ago
Richard Belleville	273ed1fea0	Make patch work for downstream dependencies	4 years ago
Guantao Liu	6b8a71ef40	Add a new submodule "libuv"	5 years ago
Richard Belleville	7b2c8c27b0	Separate py_grpc_library and py_proto_library. By popular demand, we'll now be offering separate py_grpc_library and py_proto_library targets sharing the same interface as within google3. This change necessitated some modifications to how we pull in our own Python-level dependencies and how we make those available to those pulling in our project via Bazel. There is now a grpc_python_deps() Bazel workspace rule that pulls in the appropriate dependencies, which should be called from the client project's WORKSPACE file. A test has been added to the bazel/test/ directory to verify that this behavior works as intended. It's worth noting that the protobuf repository's usage of Starlark bind() caused a great deal of trouble in ensuring that we could also pull in six. This change also required a change in the way generated proto code is imported in the channelz and health-check modules, as well as in their associated tests. We were importing them two different ways, each relative. This resulted in two different module objects being imported into the process, which were incompatible. I am not sure exactly what caused this behavior to begin, as this should have been possible before this PR. As a workaround, I am simply trying two different absolute imports and using the one that works. This should function both inside and outside of Bazel environments.	5 years ago
Esun Kim	ded9f46c06	Refactored BUILD file to isolate cronet rules	5 years ago
Bill Feng	e9ad9e90b3	reinstated version bump of google benchmark	6 years ago
Jan Tattermusch	cf6a311761	Revert "Windows builds for gRPC C++ tests"	6 years ago
billfeng327	5eb1e8d8c9	code cleanup, removed old build file	6 years ago
Naresh	11f199e34d	Workspace changes to build gRPC Python with Bazel - Include new rules from bazelbuild/rules_python, which allow for importing pip dependencies with Bazel. - Make Cython BUILD file visible to WORKSPACE. - Use a custom requirements file for Bazel python. This is added to allow for requirements previously added only during build steps.	6 years ago
Alex Polcyn	aa56034b58	Add python bazel deps needed to run resolver component tests	7 years ago
Ning Ren	4856782510	Packs contents of WORKSPACE into a bzl function, so that it can be resued by other projects, and simplifies cares build.	7 years ago
Ning Ren	174e02ae3e	Packs contents of WORKSPACE into a bzl function, so that it can be resued by other projects, and simplifies cares build.	7 years ago

12 Commits (7e5f2579254c1790ac275c176638fb89402a969d)