Skip to content
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

#21745: set timeout for closing worker session #24193

Merged
merged 1 commit into from Dec 10, 2018

Conversation

lxl910915
Copy link
Contributor

@lxl910915 lxl910915 commented Dec 6, 2018

#21745: set timeout for closing worker session

@ymodak ymodak self-assigned this Dec 6, 2018
@ymodak ymodak requested a review from mrry December 6, 2018 19:34
@ymodak ymodak added the awaiting review Pull request awaiting review label Dec 6, 2018
@mrry mrry requested review from saeta and removed request for mrry December 8, 2018 01:32
@mrry
Copy link
Contributor

mrry commented Dec 8, 2018

Transferring this PR to @saeta, since it affects things he is interested in, and I'm not going to have time to look at it.

@saeta saeta added the kokoro:force-run Tests on submitted change label Dec 10, 2018
@kokoro-team kokoro-team removed the kokoro:force-run Tests on submitted change label Dec 10, 2018
@ymodak ymodak added ready to pull PR ready for merge process and removed awaiting review Pull request awaiting review labels Dec 10, 2018
pull bot pushed a commit to Rachelmorrell/tensorflow that referenced this pull request Dec 10, 2018
@tensorflow-copybara tensorflow-copybara merged commit 7667f97 into tensorflow:master Dec 10, 2018
@lxl910915 lxl910915 deleted the worker-timeout branch December 11, 2018 03:02
tensorflow-copybara pushed a commit that referenced this pull request Dec 20, 2018
@byronyi
Copy link
Contributor

byronyi commented Dec 27, 2018

This has been reverted in 148047b. Anything broken by this?

Ping @saeta

@legatoo
Copy link

legatoo commented Apr 4, 2019

@saeta +1, why this patch is reverted?

@mrry
Copy link
Contributor

mrry commented Apr 4, 2019

The patch was causing segfaults, I think because of a use-after-free bug: the callbacks would still be called after the function returned, accessing the stack-allocated workers vector.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes ready to pull PR ready for merge process
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

9 participants