© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Ah I see. I think there might be two fixes needed.
Situation One:
* A test starts to run, and some test case results are recorded. For what ever reason the test hangs, and then timeouts.
Situation Two:
* A test starts to run, but no test case results are record, as the test case hung before any were produced.
In the case on #1, I think we should display both error messages. One at the test result level (like your example), and at the test case result level. Obviously in case #2 an error message, an error message at the test result level is all that is needed.