-
Notifications
You must be signed in to change notification settings - Fork 320
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
Add scala Future test case using multiple threads #1918
Conversation
❕ Build Aborted
Expand to view the summary
Build stats
🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
Could someone have another look at this or will this wait until there is a decision on how to support community plugins? |
@felixbarny Any progress on this? :) |
Hi! We just realized that we haven't looked into this issue in a while. We're sorry! We're labeling this issue as |
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! |
@botelastic[bot] is not allowed to run commands |
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