Differences between revisions 2 and 3
Revision 2 as of 2017-12-01 15:58:21
Size: 2787
Comment: update exit codes
Revision 3 as of 2017-12-03 17:30:10
Size: 2969
Comment: update exit codes
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
We use the following exit codes, listing the names as used in [[http://hg.fast-downward.org/file/tip/src/search/utils/system.h|src/search/utils/system.h]] and [[http://hg.fast-downward.org/file/tip/driver/returncodes.py|driver/returncodes.py]]. They are grouped in four blocks. Fast Downward returns the following positive exit codes, listing the names as used in [[http://hg.fast-downward.org/file/tip/src/search/utils/system.h|src/search/utils/system.h]] and [[http://hg.fast-downward.org/file/tip/driver/returncodes.py|driver/returncodes.py]]. If it gets killed by a specific signal, it returns the signal as exit code, except for SIGXCPU which we intercept. The exit codes we defined are grouped in four blocks. 
Line 7: Line 7:
The first block (0-9) represents succesful termination of a component which does not prevent the execution of further components. The first block (0-9) represents successful termination of a component which does not prevent the execution of further components.
Line 11: Line 11:
|| 1 || SEARCH_PLAN_FOUND_AND_OUT_OF_MEMORY || Only for portfolios: at least one plan was found and another component ran out of memory. ||
|| 2 || SEARCH_PLAN_FOUND_AND_OUT_OF_TIME || Only for portfolios: at least one plan was found and another component ran out of time. ||
|| 3 || SEARCH_PLAN_FOUND_AND_OUT_OF_MEMORY_AND_TIME || Only for portfolios: at least one plan was found, another component ran out of memory, and yet another one ran out of time. ||
|| 1 || SEARCH_PLAN_FOUND_AND_OUT_OF_MEMORY || Only returned by portfolios: at least one plan was found and another component ran out of memory. ||
|| 2 || SEARCH_PLAN_FOUND_AND_OUT_OF_TIME || Only returned by portfolios: at least one plan was found and another component ran out of time. ||
|| 3 || SEARCH_PLAN_FOUND_AND_OUT_OF_MEMORY_AND_TIME || Only returned by portfolios: at least one plan was found, another component ran out of memory, and yet another one ran out of time. ||
Line 15: Line 15:
The second block (10-19) represents unsuccesful, but error-free termination which prevents the execution further components The second block (10-19) represents unsuccessful, but error-free termination which prevents the execution further components
Line 24: Line 24:
|| 21 || TRANSLATE_OUT_OF_TIME || Time exhausted. Only supported under Linux because we use SIGXCPU to kill the planner. || || 21 || TRANSLATE_OUT_OF_TIME || Time exhausted. Not supported on Windows because we use SIGXCPU to kill the planner. ||
Line 26: Line 26:
|| 23 || SEARCH_OUT_OF_TIME || Timeout occured. Only supported under Linux because we use SIGXCPU to kill the planner. ||
|| 24 || SEARCH_OUT_OF_MEMORY_AND_TIME || Only returned by portfolios if one component ran out of memory and another one out of time. ||
|| 23 || SEARCH_OUT_OF_TIME || Timeout occurred. Not supported on Windows because we use SIGXCPU to kill the planner. ||
|| 24 || SEARCH_OUT_OF_MEMORY_AND_TIME || Only returned by portfolios: one component ran out of memory and another one out of time. ||

Back to HomePage.

Exit Codes

Fast Downward returns the following positive exit codes, listing the names as used in src/search/utils/system.h and driver/returncodes.py. If it gets killed by a specific signal, it returns the signal as exit code, except for SIGXCPU which we intercept. The exit codes we defined are grouped in four blocks.

The first block (0-9) represents successful termination of a component which does not prevent the execution of further components.

Code

Name

Meaning

0

SUCCESS

All run components successfully terminated (translator: completed, search: found a plan, validate: validated a plan)

1

SEARCH_PLAN_FOUND_AND_OUT_OF_MEMORY

Only returned by portfolios: at least one plan was found and another component ran out of memory.

2

SEARCH_PLAN_FOUND_AND_OUT_OF_TIME

Only returned by portfolios: at least one plan was found and another component ran out of time.

3

SEARCH_PLAN_FOUND_AND_OUT_OF_MEMORY_AND_TIME

Only returned by portfolios: at least one plan was found, another component ran out of memory, and yet another one ran out of time.

The second block (10-19) represents unsuccessful, but error-free termination which prevents the execution further components

10

TRANSLATE_UNSOLVABLE

Translator proved task to be unsolvable. Currently not used

11

SEARCH_UNSOLVABLE

Task is provably unsolvable with current bound. Currently only used by hillclimbing search. See also issue377.

12

SEARCH_UNSOLVED_INCOMPLETE

Search ended without finding a solution.

The third block (20-29) represents expected failures which prevents the execution further components

20

TRANSLATE_OUT_OF_MEMORY

Memory exhausted.

21

TRANSLATE_OUT_OF_TIME

Time exhausted. Not supported on Windows because we use SIGXCPU to kill the planner.

22

SEARCH_OUT_OF_MEMORY

Memory exhausted.

23

SEARCH_OUT_OF_TIME

Timeout occurred. Not supported on Windows because we use SIGXCPU to kill the planner.

24

SEARCH_OUT_OF_MEMORY_AND_TIME

Only returned by portfolios: one component ran out of memory and another one out of time.

The fourth block (30-39) represents unrecoverable failures which prevents the execution further components

30

TRANSLATE_CRITICAL_ERROR

Critical error: something went wrong (e.g. translator bug, but also malformed PDDL input)

31

TRANSLATE_INPUT_ERROR

Usage error: wrong command line options

32

SEARCH_CRITICAL_ERROR

Something went wrong that should not have gone wrong (e.g. planner bug).

33

SEARCH_INPUT_ERROR

Wrong command line options or SAS+ file.

34

SEARCH_UNSUPPORTED

Requested unsupported feature.

FastDownward: ExitCodes (last edited 2021-06-03 20:28:45 by JendrikSeipp)