-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CacheResourcesManagerTest.testAvailableCache fails sometimes #753
Comments
I'd be interested in investigating this. It happens on my local machine as well. |
I was having some issues reproducing it on my local machine. On a Fedora VM where I limit the bandwidth access, Another way to go about this (cleaner implementation, which requires a lot more changes and is probably not feasible) is to return a |
Instead of waiting a fixed amount of time for a download, the cache tests use repeated polling to check if the download has finished. This means that on fast systems, the tests will run faster, and on slow systems there should be less random failure. Fixes eclipse-lemminx#753 Signed-off-by: David Thompson <[email protected]>
I tried again with I also tried with |
Instead of waiting a fixed amount of time for a download, the cache tests use repeated polling to check if the download has finished. This means that on fast systems, the tests will run faster, and on slow systems there should be less random failure. Fixes eclipse-lemminx#753 Signed-off-by: David Thompson <[email protected]>
Instead of waiting a fixed amount of time for a download, the cache tests use repeated polling to check if the download has finished. This means that on fast systems, the tests will run faster, and on slow systems there should be less random failure. Fixes eclipse-lemminx#753 Signed-off-by: David Thompson <[email protected]>
Instead of waiting a fixed amount of time for a download, the cache tests use repeated polling to check if the download has finished. This means that on fast systems, the tests will run faster, and on slow systems there should be less random failure. Fixes eclipse-lemminx#753 Signed-off-by: David Thompson <[email protected]>
Instead of waiting a fixed amount of time for a download, the cache tests use repeated polling to check if the download has finished. This means that on fast systems, the tests will run faster, and on slow systems there should be less random failure. Fixes eclipse-lemminx#753 Signed-off-by: David Thompson <[email protected]>
Instead of waiting a fixed amount of time for a download, the cache tests use repeated polling to check if the download has finished. This means that on fast systems, the tests will run faster, and on slow systems there should be less random failure. Fixes eclipse-lemminx#753 Signed-off-by: David Thompson <[email protected]>
Use a CompletableFuture to wait for the download to finish when testing the CacheResourceManager. This should mean different CPU/network conditions don't cause the tests to fail. A generous timeout is given for the downloads. Fixes eclipse-lemminx#753 Signed-off-by: David Thompson <[email protected]>
Use a CompletableFuture to wait for the download to finish when testing the CacheResourceManager. This should mean different CPU/network conditions don't cause the tests to fail. A generous timeout is given for the downloads. Fixes eclipse-lemminx#753 Signed-off-by: David Thompson <[email protected]>
Use a CompletableFuture to wait for the download to finish when testing the CacheResourceManager. This should mean different CPU/network conditions don't cause the tests to fail. A generous timeout is given for the downloads. Fixes #753 Signed-off-by: David Thompson <[email protected]>
The Junit test CacheResourcesManagerTest.testAvailableCache fails sometimes in CI build. I suspect that several PR uses the same folder to check file is not downloaded. I think teh fix is to use a temporar file to download XSD, DTD files to test.
The text was updated successfully, but these errors were encountered: