From 742aed8c6069ef8ddb59386b4d9f92e3b564bc8c Mon Sep 17 00:00:00 2001 From: Austin Anderson <angerson@google.com> Date: Wed, 18 May 2022 16:10:35 -0700 Subject: [PATCH] Fix a typo --- devinfra_windows_rbe/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/devinfra_windows_rbe/README.md b/devinfra_windows_rbe/README.md index 636fbb1..df4681d 100644 --- a/devinfra_windows_rbe/README.md +++ b/devinfra_windows_rbe/README.md @@ -51,7 +51,7 @@ build:rbe_win --extra_toolchains="//tensorflow/tools/toolchains/win/tf_win_06242 For the RBE container, we would upload the new container to a GCP Docker repo and update our RBE configuration rule in -[`//tensorflow/tools/toolchains/win/BUILD`](http://github.com/tensorflow/tensorflow/tree/master/tensorflow/toolchains/win/BUILD). +[`//tensorflow/tools/toolchains/win/BUILD`](http://github.com/tensorflow/tensorflow/tree/master/tensorflow/tools/toolchains/win/BUILD). with the new hash. You can see the identifier `rbe_windows_ltsc2019` in our [`.bazelrc`](http://github.com/tensorflow/tensorflow/tree/master/.bazelrc). Past that, I'm not really sure about how Bazel does RBE environment selection. -- GitLab