-
Notifications
You must be signed in to change notification settings - Fork 445
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
Kill custom threadpools #1461
Kill custom threadpools #1461
Conversation
Refer to this link for build results (access rights to CI server needed): |
5d7904a
to
1ce2c59
Compare
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
I'm guessing this is not ok
expected 5s, called in 0s. |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
65ab79b
to
f2740e1
Compare
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
# runs on the reactor | ||
def session_getstate_usercallback_target(): | ||
(when, getpeerlist) = usercallback(ds) | ||
with self.dllock: |
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.
this one doesn't make a lot of sense anymore
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.
You mean acquiring the lock?
Refer to this link for build results (access rights to CI server needed): |
By not using TwistedRawServer.perform_getstate_usercallback() Simplifies code and allows us to remove that weird one as it's only used in two places in Tribler.
In favor of a generic method in twisted_thread.
In favor of using the generic callInThreadPool().
And don't create task ID's as TwistedRawServer will create them for us.
So it has the same signature than add_tast_in_thread
Save some scheduling latency.
So we can implement a blocking stop() method later that waits for all the tasks to be done.
b52f211
to
9e18a49
Compare
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
The job's timeout threshold got set too low due to @rjruigrok improvements on the tunnel tests. |
retest this please |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
@LipuFei @NielsZeilemaker ready |
No description provided.