benchmarks: Remove unnecessary volatile from TransportBenchmark

TearDown is guaranteed to execute after Setup; there is no synchronization
necessary. Although the volatile doesn't hurt anything functionally, it is
misleading and confusing.
This commit is contained in:
Eric Anderson 2018-02-17 10:15:06 -08:00
parent a919ef7f74
commit 0aaaacec83
1 changed files with 1 additions and 1 deletions

View File

@ -69,7 +69,7 @@ public class TransportBenchmark {
private ManagedChannel channel;
private Server server;
private BenchmarkServiceGrpc.BenchmarkServiceBlockingStub stub;
private volatile EventLoopGroup groupToShutdown;
private EventLoopGroup groupToShutdown;
@Setup
@SuppressWarnings("LiteralClassName") // Epoll is not available on windows