Skip to content

Remote: Do not upload empty output to remote cache.#13594

Closed
coeuvre wants to merge 2 commits intobazelbuild:masterfrom
coeuvre:remote-dont-upload-empty-blobs
Closed

Remote: Do not upload empty output to remote cache.#13594
coeuvre wants to merge 2 commits intobazelbuild:masterfrom
coeuvre:remote-dont-upload-empty-blobs

Conversation

@coeuvre
Copy link
Copy Markdown
Member

@coeuvre coeuvre commented Jun 22, 2021

An unintended side-effect of change cc2b3ec is that zero-sized blob won't be uploaded to gRPC cache. However, the behavior is existed for a long time and the REAPI spec is also updated accordingly. This change makes the behavior explicit and brings it to other remote cache backends.

Context #11063.

Fixes #13349.

@google-cla google-cla Bot added the cla: yes label Jun 22, 2021
@coeuvre coeuvre requested a review from philwo June 22, 2021 09:19
@philwo
Copy link
Copy Markdown
Member

philwo commented Jun 22, 2021

Interesting! 🤔 But if it's in the spec, yeah, why not. ^^

@coeuvre coeuvre mentioned this pull request Jun 28, 2021
9 tasks
@coeuvre coeuvre mentioned this pull request Jul 8, 2021
@bazel-io bazel-io closed this in 18c8216 Jul 13, 2021
coeuvre added a commit to coeuvre/bazel that referenced this pull request Jul 15, 2021
An unintended side-effect of change cc2b3ec is that zero-sized blob won't be uploaded to gRPC cache. However, the behavior is existed for a long time and the REAPI spec is also updated accordingly. This change makes the behavior explicit and brings it to other remote cache backends.

Context bazelbuild#11063.

Fixes bazelbuild#13349.

Closes bazelbuild#13594.

PiperOrigin-RevId: 384457129
coeuvre added a commit to coeuvre/bazel that referenced this pull request Jul 15, 2021
An unintended side-effect of change cc2b3ec is that zero-sized blob won't be uploaded to gRPC cache. However, the behavior is existed for a long time and the REAPI spec is also updated accordingly. This change makes the behavior explicit and brings it to other remote cache backends.

Context bazelbuild#11063.

Fixes bazelbuild#13349.

Closes bazelbuild#13594.

PiperOrigin-RevId: 384457129
coeuvre added a commit to coeuvre/bazel that referenced this pull request Jul 15, 2021
An unintended side-effect of change cc2b3ec is that zero-sized blob won't be uploaded to gRPC cache. However, the behavior is existed for a long time and the REAPI spec is also updated accordingly. This change makes the behavior explicit and brings it to other remote cache backends.

Context bazelbuild#11063.

Fixes bazelbuild#13349.

Closes bazelbuild#13594.

PiperOrigin-RevId: 384457129
coeuvre added a commit to coeuvre/bazel that referenced this pull request Jul 15, 2021
An unintended side-effect of change cc2b3ec is that zero-sized blob won't be uploaded to gRPC cache. However, the behavior is existed for a long time and the REAPI spec is also updated accordingly. This change makes the behavior explicit and brings it to other remote cache backends.

Context bazelbuild#11063.

Fixes bazelbuild#13349.

Closes bazelbuild#13594.

PiperOrigin-RevId: 384457129
coeuvre added a commit to coeuvre/bazel that referenced this pull request Jul 16, 2021
An unintended side-effect of change cc2b3ec is that zero-sized blob won't be uploaded to gRPC cache. However, the behavior is existed for a long time and the REAPI spec is also updated accordingly. This change makes the behavior explicit and brings it to other remote cache backends.

Context bazelbuild#11063.

Fixes bazelbuild#13349.

Closes bazelbuild#13594.

PiperOrigin-RevId: 384457129
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

/dev/null in action cache, remote caches, etc ( /cas/e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 )

2 participants