Clean up expected exception tests
in preparation for a change[]
Previously calls to @CheckReturnValue-annotated methods were ignored in tests
that used ExpectedException. The enforcement is being changed to only ignore
calls that immediately follow a call to ExpectedException#expect to improve
performance.
Also note that using `assertThrows` or `expectThrows` instead of
`ExpectedException` is now strongly recommended:
[]
Tested:
TAP --sample for global presubmit queue
[]
PiperOrigin-RevId: 164457920
diff --git a/src/test/java/com/google/devtools/build/lib/bazel/repository/downloader/HttpConnectorMultiplexerIntegrationTest.java b/src/test/java/com/google/devtools/build/lib/bazel/repository/downloader/HttpConnectorMultiplexerIntegrationTest.java
index 875501b..df81dbe 100644
--- a/src/test/java/com/google/devtools/build/lib/bazel/repository/downloader/HttpConnectorMultiplexerIntegrationTest.java
+++ b/src/test/java/com/google/devtools/build/lib/bazel/repository/downloader/HttpConnectorMultiplexerIntegrationTest.java
@@ -203,7 +203,7 @@
ServerSocket server2 = new ServerSocket(0, 1, InetAddress.getByName(null));
ServerSocket server3 = new ServerSocket(0, 1, InetAddress.getByName(null))) {
for (final ServerSocket server : asList(server1, server2, server3)) {
- executor.submit(
+ Future<?> unused = executor.submit(
new Callable<Object>() {
@Override
public Object call() throws Exception {
