Yun Peng

@gregmagolan Can you send a PR to the `release-6.0.0` branch?

**Update**: Three regressions are reported for the latest RC: https://github.com/bazelbuild/bazel/milestone/38 The team is working on fixing them and the 6.0 release will be delayed.

The docker container with the latest Bazel version is already published to gcr.io/bazel-public/bazel

I'm cleaning up the `6.0.0 nice to have` label, do we still want to cherry pick this change into the next 6.x release? If so, feel free to mark it!

Nice!

SGTM, and I believe we have the `oldName` attribute for a flag, so that users still depend on `--experimental_remote_build_event_upload` won't be broken at all. For example, https://github.com/bazelbuild/bazel/blob/9f2cc569c26914a96337525022a73ded515df813/src/main/java/com/google/devtools/build/lib/packages/semantics/BuildLanguageOptions.java#L201

> We solve the problem by checking - if a test_path does not exist, then we use $(cwd)/$(test_path) - which will point to @bazel_tools under execroot/.../external/bazel_tools/... This sounds very brittle,...

I don't think this is a breaking change, I think we can get it cherry picked for 6.1

@bazel-io fork 6.1.0

Looks like the alternative change is already in 6.0.0, so I'll close this one