-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Labels
enhancementNew feature or requestNew feature or request
Description
As a workflow developer, I would like to be notified about non-standard terminations of the flex part code. That would be a prerequisite for creating the base restart workflow.
Here are the suggestions from @ayanu on which exit strings should be parsed by the code plugin:
| String to search for | description | category | action |
|---|---|---|---|
| ERROR | General FLEXPART model error with error message | Identified model error | parse all lines continuing string back to AiiDA? |
| Execution terminated | General FLEXPART model error with error message | Identified model error | parse all lines continuing string back to AiiDA? |
| Execution is terminated | General FLEXPART model error with error message | Identified model error | parse all lines continuing string back to AiiDA? |
| Could not allocate | Model not able to allocate required memory | Identified model error | parse all lines containing the string to AiiDA? |
| Sorry | General FLEXPART model error with error message | Identified model error | parse all lines continuing string back to AiiDA? |
| NOT CONSISTENT | Newly read inputs are on a different grid than previous fields | Identified model error | parse all lines containing string back to AiiDA? |
| CONGRATULATIONS | Model finished without any identified error | Model success | Indicate success |
| None of the above | Model terminated without meaningful error message | Unknown model error | parse last 10 lines of stdout |
Close the issue when all the mentioned errors are parsed.
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or request