-
Notifications
You must be signed in to change notification settings - Fork 32
Caraya Error Codes
Francois Normandin edited this page Apr 12, 2020
·
9 revisions
This page contains a table of the error codes used in the Caraya framework.
We've choosen to use error codes starting with 7000 and separated the codes in sub-categories. For backward-compatibility reasons, the default Assert error will remain error 1, since it is user-overridable.
- 1: Assertion error; "ASSERTATION FAILED: %s"
- 7:
- 42: Nested Test Suites are not supported; "A test is already defined. Nested Test Suites are not supported"
- 7000: Generic Test Manager error (ex: Unhandled state)
- 7001: Non-existent User Application Data folder
- 7002: Test Suite failed
- 7003: Test Manager shutdown timed out
- 7004: Cannot find assertion's caller path
- 7005: Cannot open assertion's caller block diagram
- 7100: Cannot use the linker info in the Run time engine.
- 7101: At least one test is not in an executable state.
- 7102: At least one test is not in a scope that allows it to be run programmatically.
- 7103: Project reference is invalid
- 7104: Function is not available in a real-time target
- 7105: Invalid or non-existent path
- 7106: Unsupported file type
- 7107: Undefined object
- 7200: Generic Test Manager error (ex: Unhandled state)
- 7230: Generic Test Report error
- 7231: Invalid report path
- 7232: Report path is empty or relative. Use an absolute path.
- 7233: Unexpected file type.
- 7234: Directory not found.