Closed lefou closed 3 months ago
The problem with this approach is that the Future
is not cancelled, so the other runs will run concurrently with the first.
The problem with this approach is that the
Future
is not cancelled, so the other runs will run concurrently with the first.
How about using a Java future, which is cancellable?
I'm not very familiar with it, but if it's cancelable it is better, yes. Otherwise you need to run a Thread
and handle it manually.
The idea is, that our example integration tests should finish after a short period of time. But sometimes then hang in CI, so we simply abort and retry them automatically, instaed of manually.
The hardcoded timeout of 5 minutes is just a guess. I want to see the CI results. Maybe, we can make it configurable per test suite.