Bazel head breaks RBE tests

[agoulti]

This is a tracking bug to ensure that all the fixes are cherrypicked into the release.

[meisterT]

Can you please be more specific. What is broken, what needs to be cherry picked? Is it broken in 4.0?

[meisterT]

cc @philwo

[coeuvre]

This is referring to recent changes to output paths semantics.

These changes aren't included in 4.1 release but in the future if we release 7149f57, make sure to include others 24c980b, e6f1066, 4efeac9 and #13339.

[katre]

@coeuvre Can you confirm that this is fine and the needed cherrypicks are present?

[coeuvre]

Yes, the needed cherrypicks are included.

[sethkoehler]

Just to verify, I was clicking on the cherrypicks and the last one was a PR (#13339). Unlike the other entries (e.g., 4efeac9), I didn't see a label indicating this was included in 5.0.0-pre.20210708.4 (when I clicked on specific commits in https://github.com/bazelbuild/bazel/pull/13339/commits), I noticed there was a warning banner saying certain commits weren't included in any release (e.g., 6636dc2)? I am probably using github wrong (I don't have much experience with it), but just wanted to double check the last set of commits really is included in the release?

[katre]

@sethkoehler Because of the degree of divergence between 4.2.0 and 5.0.0-pre, the commits require changes to merge cleanly. This changes the commit id and causes git to report that it is only on the release branch. These are still cherrypicked commits from the master branch on bazelbuild/bazel.

Some commits are also fixes for specific release blockers and may not yet be in a released version of Bazel.

[sethkoehler]

Ok, glad to hear all is well, thank you for confirming those commits are indeed in the upcoming 5.0.0 release!