https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-764 Lustre <p><a href="https://maloo.whamcloud.com/test_sets/657179ce-e58c-11e0-9909-52540025f9af" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/657179ce-e58c-11e0-9909-52540025f9af</a></p> <p>All subtests are PASS but the test is marked as FAIL</p> Lustre Clients: <br/> Tag: v2_1_0_0_RC2<br/> Distro/Arch: Sles11/x86_64 (kernel version: 2.6.32.43-0.4-default) <br/> Build: <a href="https://build.whamcloud.com/job/lustre-master/arch=x86_64,build_type=client,distro=sles11,ib_stack=inkernel/">https://build.whamcloud.com/job/lustre-master/arch=x86_64,build_type=client,distro=sles11,ib_stack=inkernel/</a><br/> Network: TCP<br/> ENABLE_QUOTA=yes <br/> <br/> Lustre Servers:<br/> Tag: v2_1_0_0_RC2<br/> Distro/Arch: RHEL6/x86_64 (kernel version: 2.6.32-131.6.1.el6)<br/> Build: <a href="https://build.whamcloud.com/job/lustre-master/283/arch=x86_64,build_type=cserver,distro=el6,ib_stack=inkernel/">https://build.whamcloud.com/job/lustre-master/283/arch=x86_64,build_type=cserver,distro=el6,ib_stack=inkernel/</a><br/> Network: TCP<br/> LU-764

test marked as fail but all subtest pass

Bug Major Resolved Not a Bug Minh Diep Minh Diep Fri, 23 Sep 2011 01:49:02 +0000 Thu, 21 Mar 2013 16:52:27 +0000 Thu, 21 Mar 2013 16:52:27 +0000 0 3 <p>We traced this down to the frame-work in Lustre, it writes the incorrect info to results.yml</p> <p>I have checked recent reports for this test and haven't seen a failure</p> <p>actually, ost_pools test has 30 to 31 subtest and this report show only 22 subtests and duration is over 3600s. I believe that the test timed out by autotest but did not marked as TIMEOUT.</p> <p>Chris,</p> <p>I think you have worked or increased the timeout value. I think this bug can be closed. what do you think?</p> <p>Haven't seen this in a while, reopen if reproducible</p> <p>I am seeing this with a b1_8 patch. </p> <p><a href="https://maloo.whamcloud.com/test_sessions/67735464-3c51-11e2-82b5-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sessions/67735464-3c51-11e2-82b5-52540035b04c</a></p> <p>recovery-small shows all green but report fail. It looks like there was an initial failure that somehow cascaded to tests passing but then being marked failed. </p> <p>The report shows that all subtest passed which is correct. However, at the end of the test, there is a cleanup which failed. I think this results in the entire testsuite being marked failed. It's debatable if this is an error/bug because obviously a failure occur but not in the subtest. I think this is a good/correct behavior.</p> <p>I agree if there is an error in anyway it should be marked as failed. We don't want to ignore errors. </p> <p>Should the subtest have a way to mark "cleanup failed"?</p> <p>Unfortunately the way each subtest is run, and the clean up is outside of the subtest, I don't think we can mark it failed in the subtest level</p> <p>I have seen a bit of this over the last week or so on master. This is a good example. </p> <p><a href="https://maloo.whamcloud.com/test_sessions/bf361f32-8919-11e2-b643-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sessions/bf361f32-8919-11e2-b643-52540035b04c</a></p> <p>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? </p> <p>Starting to see this a bit on current master. </p> <p>I looked at the log above, sanity actually ran much longer but maloo only show a few hundreds of second<br/> == sanity test complete, duration 2584 sec == 14:03:39 (1362866619)</p> <p>I don't think this is the same problem. Please file a TT ticket.</p> Development Rank 1|hzuryf: Rank (Obsolete) 2191 Severity