You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the event a testcase fails to execute cleanly or something else occurred on the system which affected a kyua testcase, it's very hard to diagnose what caused the failure.
The start time (GMT) should be captured. With the start time one could determine when the testcase started, how long the testcase ran, and then correlate what the exact failure was for a given issue with the system, or whether or not a testcase caused a failure on the system.
The text was updated successfully, but these errors were encountered:
ngie-eign
pushed a commit
to ngie-eign/scratch
that referenced
this issue
May 12, 2015
This script is extremely helpful when trying to correlate results
with syslog data
Stopgap solution until freebsd/kyua#139 has
been fixed
Sponsored by: EMC / Isilon Storage Division
The start and end times of each test case are already recorded in the database; see the test_results table in store/schema_v3.sql. Mind you, this is how the run time of each test and the whole test suite is computed. We "just" need to extend the various report commands to do something with this information.
E.g. it'd be trivial to get kyua report --verbose to output these details for each test, if you are interested in giving this a go :-P
Version: 0.8/0.11
In the event a testcase fails to execute cleanly or something else occurred on the system which affected a kyua testcase, it's very hard to diagnose what caused the failure.
The start time (GMT) should be captured. With the start time one could determine when the testcase started, how long the testcase ran, and then correlate what the exact failure was for a given issue with the system, or whether or not a testcase caused a failure on the system.
The text was updated successfully, but these errors were encountered: