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

SystemError on running MDStudio workflows with two different specializations #80

Closed
marcvdijk opened this issue Dec 4, 2018 · 2 comments
Assignees
Labels

Comments

@marcvdijk
Copy link
Member

After having successfully run a MDStudio LIE workflow using the GT specialization and launching another one using the LISA specialization the latter one fails in the lie_md stage with a Cerise SystemError. The docker container with the LISA specialization is started but there seems to be no connection made to it.
Once the SystemError is raised a workflow using the original GT specialization will also no longer run. The only way to recover seems to be stopping and removing the contains for the specializations.

There may be other factors involved in causing this problem but at least the is the observation I made

@felipeZ
Copy link

felipeZ commented Dec 4, 2018

The error is due to this issue in lie_md

@LourensVeen
Copy link
Member

Closing this since it's not a Cerise issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants