Add missing "fall through" comments to switches that fall through

cushon · neozwu · commit 7af7866fa2aa · 2017-06-30T15:36:53.000-07:00
The Style Guide requires that within a switch block, each statement group either terminates abruptly (e.g. with a break), or is marked with a comment to indicate that execution may "fall through" to next statement group. This change is being made in preparation for enabling a new compiler error, which will ensure a "fall through" comment is present if and only if the switch falls through. NOTE TO REVIEWERS: Please review carefully to ensure the fall through is deliberate. If it is a bug and there should e.g. be a 'break;' statement, please respond with a suggested edit. More information: https://docs.google.com/a/google.com/document/d/1cz7o7p9ROfXZ0VMtUfFN7Tnw3F61qkFw9bnJ64GDiP8/edit?usp=sharing Tested: TAP --sample for global presubmit queue http://test/OCL:147852686:BASE:147857215:1487376286182:2ba055dd ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=148101033
diff --git a/google-api-client/src/test/java/com/google/api/client/googleapis/media/MediaHttpUploaderTest.java b/google-api-client/src/test/java/com/google/api/client/googleapis/media/MediaHttpUploaderTest.java
@@ -234,6 +234,7 @@ public LowLevelHttpResponse execute() throws IOException {
                   response.addHeader("Range", "bytes=0-" + contentLength);
                   return response;
                 }
+                break;
               default:
                 break;
             }

Original file line number	Diff line number	Diff line change
`@@ -234,6 +234,7 @@ public LowLevelHttpResponse execute() throws IOException {`
`234`	`234`	`response.addHeader("Range", "bytes=0-" + contentLength);`
`235`	`235`	`return response;`
`236`	`236`	`}`
	`237`	`+ break;`
`237`	`238`	`default:`
`238`	`239`	`break;`
`239`	`240`	`}`