Closed navkast closed 3 years ago
Test failure seems unrelated.
Hi @navkast! Although it might seem unrelated, we still need the CI to be green before merging this. Try to rerun it.
That test failure might be actually related.
Same test fails on another commit currently on master: https://app.circleci.com/pipelines/github/facebook/buck/2560/workflows/a7ebb86a-6503-4595-8ad4-065bdb738627/jobs/25291
Sorry, can you bump it to 200ms? Hopefully this will help to make this test more reliable. https://github.com/facebook/buck/blob/ae8e8fc013413f0144b73971eceeff3fd6f51d6c/test/com/facebook/buck/util/concurrent/JobLimiterTest.java#L71
LGTM, thanks!
For TestNG, a
@Test
method can run concurrently using a@DataProvider
:This causes an exception in Buck as follows:
The fix is to simply move the test runner's collection of test results to be a concurrency-safe collection. I use
ConcurrentLinkedQueue
: this should be faster than explicit synchronized blocks or usingCollections.synchronizedList()
.