Bugfix: improper handling of IOException. This was triggered when we decided to change some other exception types into IOExceptions.

TESTED=unit tests
RELNOTES: n/a
PiperOrigin-RevId: 160677771

1 files changed, 3 insertions, 8 deletions

diff --git a/src/main/java/com/google/devtools/build/lib/remote/GrpcActionCache.java b/src/main/java/com/google/devtools/build/lib/remote/GrpcActionCache.java
index 23899b5549..5d7ab862e2 100644
--- a/src/main/java/com/google/devtools/build/lib/remote/GrpcActionCache.java
+++ b/src/main/java/com/google/devtools/build/lib/remote/GrpcActionCache.java
@@ -467,15 +467,10 @@ public class GrpcActionCache implements RemoteActionCache {
   Digest uploadBlob(byte[] blob) throws IOException, InterruptedException {
     Digest digest = Digests.computeDigest(blob);
     ImmutableSet<Digest> missing = getMissingDigests(ImmutableList.of(digest));
-    try {
-      if (!missing.isEmpty()) {
-        uploadChunks(1, new Chunker.Builder().addInput(blob));
-      }
-      return digest;
-    } catch (IOException e) {
-      // This will never happen.
-      throw new RuntimeException();
+    if (!missing.isEmpty()) {
+      uploadChunks(1, new Chunker.Builder().addInput(blob));
     }
+    return digest;
   }
 
   byte[] downloadBlob(Digest digest)