Test fails intermittently only in pipeline

[Johan Karlsson]

I have a test that always works locally on all machines I've tested it on, but fails now and then in the pipeline.

The test in question is written in Java and uses a thread pool with a static size of 1 to ensure that a scheduled event is fired under certain conditions. I use awaitility to await a certain state, but that state is not reached within the configured timeout.

Might threading be a problem? Is there any limit to the number threads?

[mkleint · Accepted solution]

it's very likely a threading problem. with a thread pool of one, you still have 2 threads inteacting, right? one awaiting on the result from the threadpool?

[Johan Karlsson]

Sorry, should've been clearer on that. The underlying scheduler is assigned a thread pool of size 1, the application still runs on the main thread.