-
Notifications
You must be signed in to change notification settings - Fork 2.8k
(parallel-executor): tests #2967
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
base: master
Are you sure you want to change the base?
Conversation
@xgreenx I would like to have your feedback on the tests created here that should outline the behavior of parallel executor. I'm still questioning myself about asking to the pool one time for each thread. For example in the first test scenario it means that only worker thread 1 will work and second never. Maybe if transaction source is informing when asking for example for thread 2 that there is nothing we can split the queue of thread 1 in the others. I will start implementation on top of this PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice with the TDD approach! Some nits and questions from my side. I'm primarily curious about why we use threads and synchronous channels as opposed to tokio tasks and async channels.
Beyond that, I don't spot any obvious errors.
@xgreenx in addition of my previous questions here : #2967 (comment) I would like to ask you if you have an idea on how I can re-use the same DB as for the executor tests and avoid having a circular-dependency problem like this. The existing executor tests lives in fuel-core directly and so doesn't have the problem. Is it my only way to go also ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unfortunately can only suggest readability nits at this point :)
Linked Issues/PRs
Resolve #2951
Description
All tests needed to ensure the correct behavior of the parallel-executor
Checklist
Before requesting review