Add scala Future test case using multiple threads

[milanvdm]

Related to #1274

The main issue was related to scala/bug#12089 which got introduced in Scala 2.13.0.

From what I can tell, #1274 added a new test case that actually deadlocks on 2.13.0-2.13.3. This causes some weird behavior in the new test case.

After upgrading to 2.13.6 and using the ExecutionContext.global instead of a custom ForkJoinPool, the test case passes.

I also added extra test cases with different ExecutionContexts and different approaches on ending transactions.

@henrikno

[ghost]

❕ Build Aborted

The PR is not allowed to run in the CI yet

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Reason: The PR is not allowed to run in the CI yet

• Start Time: 2021-12-08T12:39:44.209+0000

• Duration: 4 min 19 sec

• Commit: 7df14f6

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• run benchmark tests : Run the benchmark test.

• run compatibility tests : Run the JDK Compatibility test.

• run integration tests : Run the APM-ITs.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[milanvdm]

Could someone have another look at this or will this wait until there is a decision on how to support community plugins?

[milanvdm]

@felixbarny Any progress on this? :)

[botelastic]

Hi! We just realized that we haven't looked into this issue in a while. We're sorry! We're labeling this issue as stalled to make it hit our filters and make sure we get back to it in as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!

[botelastic]

Hi! This issue has been stale for a while and we're going to close it as part of our cleanup procedure. We appreciate your contribution and would like to apologize if we have not been able to review it, due to the current heavy load of the team. Feel free to re-open this issue if you think it should stay open. Thank you for your contribution!

[mergify]

@botelastic[bot] is not allowed to run commands