You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: hadoop-tools/hadoop-azure/src/test/java/org/apache/hadoop/fs/azurebfs/services/ITestReadBufferManager.java
+35-35Lines changed: 35 additions & 35 deletions
Original file line number
Diff line number
Diff line change
@@ -91,31 +91,31 @@ public void testPurgeBufferManagerForParallelStreams() throws Exception {
91
91
executorService.shutdown();
92
92
}
93
93
94
-
/*
95
-
* Since, the read from inputStream is happening in parallel thread, the
96
-
* test has to wait for the execution to get over. If we don't wait, test
97
-
* main thread will go on to do assertion where the stream execution may or
98
-
* may not happen.
99
-
*/
100
-
while (!checkIfAllExecutionCompleted(executionCompletion)) {
101
-
Thread.sleep(checkExecutionWaitTime);
102
-
}
94
+
/*
95
+
* Since, the read from inputStream is happening in parallel thread, the
96
+
* test has to wait for the execution to get over. If we don't wait, test
97
+
* main thread will go on to do assertion where the stream execution may or
98
+
* may not happen.
99
+
*/
100
+
while (!checkIfAllExecutionCompleted(executionCompletion)) {
101
+
Thread.sleep(checkExecutionWaitTime);
102
+
}
103
103
104
-
/*
105
-
* The close() method of AbfsInputStream would lead to purge of completedList.
106
-
* Because the readBufferWorkers are running in parallel thread, due to race condition,
107
-
* after close and before assert, it can happen that processing of inProgress buffer
108
-
* can get completed and hence we cannot assert on completedList to be empty.
109
-
* That is why completedList are checked to not have a buffer other than the
110
-
* buffers in inProgressQueue just before the closure of AbfsInputStream object.
0 commit comments