search

radical-cybertools / ExTASY

MDEnsemble
Other
1 stars 1 forks source link

ExTASY continues upon failure #158

Closed oleweidner closed 9 years ago

oleweidner commented 9 years ago

Even though a module couldn't be loaded, the execution continues:

An error occurred: No module named mdkernels
Closing session, exiting now ...
[Callback]: ComputePilot '551a6a9d6bf88ba6260c0412' state changed to Launching.

This might be a combination of an ExTASY and RP problem though?

vivek-bala commented 9 years ago

I think this is a unique case when the callback gets registered before the session.close() gets called at https://github.com/radical-cybertools/ExTASY/blob/devel/src/radical/ensemblemd/extasy/bin/runme.py#L214.

vivek-bala commented 9 years ago

ExTASY terminates after the above callback (might take sometime though). It prints the callback, since the callback is executed before the session close. Added an import test now to avoid this.