Fix an issue that `incompatible_remote_build_event_upload_respect_no_… #16023
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…cache` doesn't work with BwtB
|
@bazel-io flag |
bazel-io
added
the
potential release blocker
|
@bazel-io fork 5.3.0 |
1 similar comment
|
@bazel-io fork 5.3.0 |
bazel-io
removed
the
potential release blocker
sgowroji
added
team-Remote-Exec
|
Hi @coeuvre, Is it possible for you to get the PR review done? Since we will be merging it under the release 5.3.0. |
tjgq
approved these changes
Aug 4, 2022
sgowroji
pushed a commit
to sgowroji/bazel
that referenced
this pull request
Aug 4, 2022
…cache` doesn't work with BwtB. The root cause is we use `Path` as key to check which files are omitted, but it also compares the underlying filesystem. When BwtB is enabled, the filesystem for the file is different so we failed to mark the file as omitted. This change fixes that by using `PathFragment` as key. Fixes bazelbuild#15527. Closes bazelbuild#16023. PiperOrigin-RevId: 465284879 Change-Id: I49bbd7a6055e0f234b4ac86a224886bd85797f71
sgowroji
added a commit
that referenced
this pull request
Aug 4, 2022
#16045) * Fix an issue that `incompatible_remote_build_event_upload_respect_no_… …cache` doesn't work with BwtB. The root cause is we use `Path` as key to check which files are omitted, but it also compares the underlying filesystem. When BwtB is enabled, the filesystem for the file is different so we failed to mark the file as omitted. This change fixes that by using `PathFragment` as key. Fixes #15527. Closes #16023. PiperOrigin-RevId: 465284879 Change-Id: I49bbd7a6055e0f234b4ac86a224886bd85797f71 * Update ByteStreamBuildEventArtifactUploader changes Removing the import as it is throwing the error Co-authored-by: Chi Wang <chiwang@google.com>
ShreeM01
added a commit
that referenced
this pull request
Aug 9, 2022
* Updated Codeowners file (#16032) * Propagate the error message when a credential helper fails. (#16030) Closes #16012. PiperOrigin-RevId: 464732834 Change-Id: If51ce914098ff17ffe23fa4614947e7f4a5088dc Co-authored-by: Tiago Quelhas <tjgq@google.com> * Migrate legacy desugar wrapper to new rlocation() (#16025) RELNOTES: Fix for desugaring failure on Bazel+Android+Windows build scenario. PiperOrigin-RevId: 464654335 Change-Id: I845093b134dc68ae541603008fe7fee701c7451c Co-authored-by: Gowroji Sunil <48122892+sgowroji@users.noreply.github.com> * Correctly report errors thrown by CommandLinePathFactory#create. (#16036) This method is called while initializing the remote module [1]. Any exceptions not derived from java.io.IOException cause a silent server crash. [1] https://cs.opensource.google/bazel/bazel/+/master:src/main/java/com/google/devtools/build/lib/remote/RemoteModule.java;l=436;drc=f3211f00ae08746b5794ab01d404c32b43146aba Closes #16022. PiperOrigin-RevId: 464997904 Change-Id: I87fd5eaeb562d849bb830d68f1bfbbf06f6e0ea9 Co-authored-by: Tiago Quelhas <tjgq@google.com> * Fix an issue that `incompatible_remote_build_event_upload_respect_no_… (#16045) * Fix an issue that `incompatible_remote_build_event_upload_respect_no_… …cache` doesn't work with BwtB. The root cause is we use `Path` as key to check which files are omitted, but it also compares the underlying filesystem. When BwtB is enabled, the filesystem for the file is different so we failed to mark the file as omitted. This change fixes that by using `PathFragment` as key. Fixes #15527. Closes #16023. PiperOrigin-RevId: 465284879 Change-Id: I49bbd7a6055e0f234b4ac86a224886bd85797f71 * Update ByteStreamBuildEventArtifactUploader changes Removing the import as it is throwing the error Co-authored-by: Chi Wang <chiwang@google.com> Co-authored-by: Tiago Quelhas <tjgq@google.com> Co-authored-by: Ted <tedx@google.com> Co-authored-by: Gowroji Sunil <48122892+sgowroji@users.noreply.github.com> Co-authored-by: Chi Wang <chiwang@google.com>
ShreeM01
removed
the
awaiting-review
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…cache` doesn't work with BwtB.
The root cause is we use
Pathas key to check which files are omitted, but it also compares the underlying filesystem. When BwtB is enabled, the filesystem for the file is different so we failed to mark the file as omitted.This change fixes that by using
PathFragmentas key.Fixes #15527.