Start running bazel C/C++ tests on mac#20510
Conversation
|
Current failures from a local run
|
|
One problem to overcome #20494 (I now understand what's going on) |
|
The other problem is that with this hack: because the thread local storage in uninitialized. E.g. |
f8350b9 to
fd4473a
Compare
6571a15 to
77e4292
Compare
|
I included the changes from #20864. |
e2c7eac to
d338162
Compare
274dd5a to
1143a8e
Compare
5cc0b5b to
770f09c
Compare
770f09c to
eb137ea
Compare
|
@veblush @rmstar this is ready for review. An adhoc run with all the tests passing: https://source.cloud.google.com/results/invocations/5c6c4d70-d6a2-491e-adf0-6b9dcb9e7d27/targets I still might need to look into test flakes, but this is good enough for a start. |
| bool restore_home_env = false; | ||
| #if defined(GRPC_BAZEL_BUILD) && \ | ||
| (defined(GPR_POSIX_ENV) || defined(GPR_LINUX_ENV)) | ||
| // when running under bazel with locally, the HOME variable is not set |
There was a problem hiding this comment.
nit: bazel with locally -> bazel locally
Setup continuous C/C++ test under bazel.
The tests are setup very similar to linux/windows RBE tests, with the exception that Foundry doesn't support Mac executors, so the tests are still built and run locally (but the test results are uploaded to result store).
I will enable the tests on PRs once the test results on master are stable.
There is also a number of fixes to the bazel tests on mac: