The C based gRPC (C++, Python, Ruby, Objective-C, PHP, C#) https://grpc.io/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Jan Tattermusch fb06f89af9 move RBE test timeout configuration to a single place 6 years ago
..
README.md use bazel --config= for all foundry builds 6 years ago
kokoro.bazelrc bazel bes_best_effort flag is deprecated 6 years ago
manual.bazelrc move RBE test timeout configuration to a single place 6 years ago
rbe_common.bazelrc move RBE test timeout configuration to a single place 6 years ago
workspace_status_kokoro.sh inject extra details to Bazel RBE links 6 years ago

README.md

Running Remote Builds with bazel

This allows you to spawn gRPC C/C++ remote build and tests from your workstation with configuration that's very similar to what's used by our CI Kokoro.

Note that this will only work for gRPC team members (it requires access to the remote build and execution cluster), others will need to rely on local test runs and tests run by Kokoro CI.

Prerequisites

Running remote build manually from dev workstation

Run from repository root (opt, dbg):

# manual run of bazel tests remotely on Foundry
bazel --bazelrc=tools/remote_build/manual.bazelrc test --config=opt //test/...

Sanitizer runs (asan, msan, tsan, ubsan):

# manual run of bazel tests remotely on Foundry with given sanitizer
bazel --bazelrc=tools/remote_build/manual.bazelrc test --config=asan //test/...

Available command line options can be found in Bazel command line reference