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

Stream is closed error upon exiting Parallel Code #10468

Closed
jakebolewski opened this issue Mar 10, 2015 · 4 comments
Closed

Stream is closed error upon exiting Parallel Code #10468

jakebolewski opened this issue Mar 10, 2015 · 4 comments

Comments

@jakebolewski
Copy link
Member

Rarely I get this error when terminating a parallel processing run. A race condition or deadlock in the distributed gc / teardown logic?

ERROR (unhandled task failure): ArgumentError: stream is closed or unusable
 in check_open at stream.jl:299
 in uv_write at stream.jl:736
 in flush at stream.jl:790
 in anonymous at multi.jl:179
 in lock at stream.jl:812
 in send_msg_ at ./multi.jl:170
 in remote_do at multi.jl:702
 in flush_gc_msgs at ./multi.jl:163
 in flush_gc_msgs at ./multi.jl:189
 in anonymous at task.jl:478

cc @amitmurthy

@andreasnoack
Copy link
Member

I'm seeing these unhandled task failures frequently now, e.g.

https://ci.appveyor.com/project/StefanKarpinski/julia/build/1.0.3101/job/ys7is66pksb5qipr

@amitmurthy
Copy link
Contributor

Dup of #10431

Is there a way to know that the process is shutting down? In normal circumstances, I would like the task failure to be printed, just needs to be ignored during exit.

@amitmurthy
Copy link
Contributor

@andreasnoack , yes, now that we are printing unhandled errors in tasks, they will show up in logs now and will need to be handled. I think it is better to create separate issues for each different error.

@pao
Copy link
Member

pao commented Mar 18, 2015

Closing as dup per @amitmurthy's comment above; reopen if I misunderstood.

@pao pao closed this as completed Mar 18, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants