Lines Matching refs:diagnostic

17 can have subtests), each of which can contain both diagnostic data -- e.g., log
19 machine-readable, whereas the diagnostic data is unstructured and is there to
73 	<result> <number> [<description>][ # [<directive>] [<diagnostic data>]]
86 The directive and any diagnostic data is optional. If either are present, they
91 keyword preceding the diagnostic data. In the event that a parser encounters
107   specific error that is included in the diagnostic data. (note the result of
110 The diagnostic data is a plain-text field which contains any additional details
114 The diagnostic data field is optional, and results which have neither a
115 directive nor any diagnostic data do not need to include the "#" field
134 The test "test" was SKIPPED with the diagnostic message "necessary dependency
141 The test "test" timed out, with diagnostic data "30 seconds".
147 The test "check return code" passed, with additional diagnostic data “rcode=0”
154 "diagnostic lines". Diagnostic lines are optional, freeform text, and are
156 more detail than the final result and diagnostic data line provides.
160 output. As a rule, diagnostic lines regarding a test are directly before the
163 Note that most tools will treat unknown lines (see below) as diagnostic lines,
166 that tests always prefix any diagnostic output they have with a "#" character.
180 thus can not print the message as a diagnostic message.
281    - "test_1", which passes, and outputs the diagnostic message "test_1: initializing test_1"
291    - "test_2", which outputs the diagnostic line "test_2: FAIL", and fails.