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

Warning: losoto multithread crash leaves pipeline hanging #2

Open
ajstewart opened this issue Feb 2, 2017 · 2 comments
Open

Warning: losoto multithread crash leaves pipeline hanging #2

ajstewart opened this issue Feb 2, 2017 · 2 comments

Comments

@ajstewart
Copy link
Contributor

This is a warning rather than an issue as I believe it needs to be corrected at the losoto end. If losoto crashes during a multithread operation the pipeline environment does not get a crash signal and just proceeds to hang. Indeed testing losoto individually also just hangs when such an error occurs.

I experienced this while running the pipeline with matplotlib v2.0.0 installed - revoltek/losoto#16.

This may be already known and can be closed if so, but I just wanted to record it somewhere.

@adrabent
Copy link
Collaborator

adrabent commented Feb 2, 2017

This issue occured already and was thought to be fixed already?
Does this issue re-occur after updaing to matplotlib v2.0.0?

@ajstewart
Copy link
Contributor Author

Yes losoto could not generate the plots because of some matplotlib file locks in v2.0.0, and the pipeline was left hanging. To get PiLL/losoto to get past this I had to downgrade to matplotlib 1.5.2 which works.

In the issue I referenced above, I reference a matplotlib issue that seems to be the cause, but I'm unclear if it's by design or an issue in matplotlib v2.0.0 that will be fixed.

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

2 participants