Test Status
Indicators
View the TTY main window Status panel for the current state
of the software. The following table describes the System Status
options.
|
|
Idle |
A test can be idle for any of the following
reasons:
Initial state of a
test. When VTS resets the tests. When you click the Stop button. When the global time limit completes and all the
tests stop.
|
Not supported |
For the given stress level, a test might
not be able to run for anyof the following reasons:
The rules file does
not define any task. The tests defined under the task (in the rules file)
were not able to probe any of the devices. When you click the Stop button. When the global time limit completes and all the
tests stop.
|
Analyzing |
A test after completion of each pass
checks for certain terminating parameters such as max time, max
pass, and max error to analyze if it can run for the next pass.
The Analyzing status lasts for two to three seconds. |
Testing |
This status indicates that the test is
currently executing. |
Completed |
This status indicates that the test has
completed its execution. The completion factor is based on the limits
set from the scheduling policy, that is, time or pass limit. |
Failed |
This status indicates that the test has
been stopped because the test errors have reached the maximum error
limit. |
Waiting for swap |
When there is not enough swap availability,
you can stop a test and schedule the test execution for later. |
Stopping |
When you press the Stop button, the test
status shows the transition from stopping status to idle state. |
|
In the GUI and TTY interfaces, the statuses are displayed
in the main window. In the CLI you get the status using the get_status
command.