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

run_serialized decorator hangs on SageMathCloud #539

Open
rjleveque opened this issue May 14, 2016 · 7 comments
Open

run_serialized decorator hangs on SageMathCloud #539

rjleveque opened this issue May 14, 2016 · 7 comments

Comments

@rjleveque
Copy link
Member

I might have raised this issue before since I first ran into this last fall, but I'm using SMC for the first time in a while and just ran into it again -- the decorator @run_serialized at line 65 of src/pyclaw/util.py has to be commented out or else visclaw/src/python/visclaw/plotpages hangs when importing this module, when trying to make plots on SMC.

@mandli
Copy link
Member

mandli commented May 14, 2016

Do you know where exactly it's hanging? We could possibly modify the decorator to return back the function if this is causing issues if we can detect when this might happen.

@rjleveque
Copy link
Member Author

The notes I made last fall indicated I thought it was a petsc problem but I don't know why I thought that...

@mandli
Copy link
Member

mandli commented May 15, 2016

It looks like pesc4py is available on sage math cloud but then hangs when it tries to initialize PETSc. I would hazard a guess that this is a bug then on SMC. Looking around I don't see an easy way to time out.

@ketch
Copy link
Member

ketch commented May 15, 2016

That's pretty annoying. The import is inside a try statement, so even if it just failed cleanly that would be fine.

@ketch
Copy link
Member

ketch commented May 15, 2016

One workaround would be to uninstall petsc4py locally, though I don't know if you have permissions to do that.

@mandli
Copy link
Member

mandli commented May 15, 2016

One of the recent PRs @rjleveque did contained an admittedly fragile way to try to figure out if someone is running on SMC. Maybe use that in the mean time and report the bug to SMC?

@ketch
Copy link
Member

ketch commented May 16, 2016

@mandli That sounds good to me.

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

3 participants