[LU-4344] Test marked FAIL with "No sub tests failed in this test set"

• Type: Bug
• Resolution: Cannot Reproduce
• Priority: Major
• Labels: support
• Environment: patches pushed to git
• Severity: 3
• Assignee: WC Triage
• Reporter: Keith Mannthey (Inactive)

Description

LU context can be found at LU-764 test marked "No sub tests failed in this test set.":

 
Keith Mannthey added a comment - 11/Mar/13 12:44 PM 
I have seen a bit of this over the last week or so on master. This is a good example.

https://maloo.whamcloud.com/test_sessions/bf361f32-8919-11e2-b643-52540035b04c

There was one real error at the very end end of this test. Other than that all subtests "passed" even though 3 whole sections are marked FAILED. What logs do you look at to see the cleanup issues previously mentioned? How can we tell if it is a problem with the patch or some autotest anomaly?
"

Minh Diep added a comment - 21/Mar/13 9:37 AM

I looked at the log above, sanity actually ran much longer but maloo only show a few hundreds of second
== sanity test complete, duration 2584 sec == 14:03:39 (1362866619)

I don't think this is the same problem. Please file a TT ticket.

This has happened a bit here an there. It would be nice to always know what failed when something "fails".

Please update the LU if this is seen as an LU issue.

Issue Links

• is related to: LU-5738 No sub tests failed even though test status is showing FAIL
• is related to: LU-5847 sanity-sec: lctl nodemap_test_nid on test_13