Skip to content

Make bazel test sharding work for poller-specific tests#21294

Merged
jtattermusch merged 1 commit intogrpc:masterfrom
jtattermusch:make_bazel_sharding_work
Nov 26, 2019
Merged

Make bazel test sharding work for poller-specific tests#21294
jtattermusch merged 1 commit intogrpc:masterfrom
jtattermusch:make_bazel_sharding_work

Conversation

@jtattermusch
Copy link
Copy Markdown
Contributor

Followup for #21274 that will actually fix #20695.

Without this, the xds_end2end_test won't actually be sharded (we're still getting the "unevaluated target" problem on master and there is only one shard: https://source.cloud.google.com/results/invocations/e7b604d6-74d2-4f6c-8768-733889379b9e/targets)

Can be verified manually with
bazel --bazelrc=tools/remote_build/manual.bazelrc test --config=ubsan //test/cpp/end2end:xds_end2end_test@poller=epollex

@jtattermusch
Copy link
Copy Markdown
Contributor Author

Known failures:
#21297

@jtattermusch jtattermusch merged commit 2324e4d into grpc:master Nov 26, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Feb 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

lang/c++ release notes: no Indicates if PR should not be in release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

//test/cpp/end2end:xds_end2end_test is flaky on UBSAN

3 participants