honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

[TEST] Make test more tolerant to slow VMs (elastic/x-pack-elasticsearch#3783) 

The test this change applies to has failed a couple of times on
Windows VMs.

Original commit: elastic/x-pack-elasticsearch@94e94d3ffd
This commit is contained in:
David Roberts 2018-01-30 16:34:16 +00:00 committed by GitHub
parent e45b738b4c
commit ce77a3dd6d
1 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
plugin/ml/src/test/java/org/elasticsearch/xpack/ml/job/process/autodetect/AutodetectProcessManagerTests.java
View File

@ -352,7 +352,12 @@ public class AutodetectProcessManagerTests extends ESTestCase {
// Also close the job in the current thread, so that we have two simultaneous close requests // Also close the job in the current thread, so that we have two simultaneous close requests
manager.closeJob(jobTask, false, "in main test thread"); manager.closeJob(jobTask, false, "in main test thread");
closeThread.join(500); // The 10 second timeout here is usually far in excess of what is required. In the vast
// majority of cases the other thread will exit within a few milliseconds. However, it
// has been observed that on some VMs the test can fail because the VM stalls at the
// wrong moment. A 10 second timeout is on a par with the length of time assertBusy()
// would wait under these circumstances.
closeThread.join(10000);
assertFalse(closeThread.isAlive()); assertFalse(closeThread.isAlive());
// Only one of the threads should have called AutodetectCommunicator.close() // Only one of the threads should have called AutodetectCommunicator.close()