[jmeter] branch master updated: No need for volatile as we are going through synchronisation

[fschumacher]

This is an automated email from the ASF dual-hosted git repository.

fschumacher pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/jmeter.git


The following commit(s) were added to refs/heads/master by this push:
     new faf94ae  No need for volatile as we are going through synchronisation
faf94ae is described below

commit faf94aefdc0576bedf98382736143d3e4d01bd63
Author: Felix Schumacher <felix.schumac...@internetallee.de>
AuthorDate: Sun Sep 29 12:29:36 2019 +0200

    No need for volatile as we are going through synchronisation
---
 src/core/src/main/java/org/apache/jmeter/report/processor/Job.java | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/core/src/main/java/org/apache/jmeter/report/processor/Job.java 
b/src/core/src/main/java/org/apache/jmeter/report/processor/Job.java
index e88ba4d..67ce390 100644
--- a/src/core/src/main/java/org/apache/jmeter/report/processor/Job.java
+++ b/src/core/src/main/java/org/apache/jmeter/report/processor/Job.java
@@ -29,11 +29,11 @@ package org.apache.jmeter.report.processor;
  */
 abstract class Job<T> implements Runnable {
 
-    private volatile boolean resultReady = false;
+    private boolean resultReady = false;
 
     private final Object lock = new Object();
 
-    private volatile T result;
+    private T result;
 
     @Override
     public final void run() {