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-7284 Lustre <p>The overall status of test script has marked failed although all sub test passed:<br/> <a href="https://testing.hpdd.intel.com/test_sets/bfdb5482-508d-11e5-95a9-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/bfdb5482-508d-11e5-95a9-5254006e85c2</a></p> shaodow LU-7284

test results marked failed although all sub test pass

Bug Minor Resolved Cannot Reproduce WC Triage Frank Heckes triage Thu, 3 Sep 2015 08:00:52 +0000 Tue, 14 Dec 2021 22:01:13 +0000 Tue, 14 Dec 2021 22:01:13 +0000 0 7 <p>Frank, looked at the results.yml file and found...</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre> name: ost-pools description: auster ost-pools submission: Tue Sep 1 06:19:40 UTC 2015 report_version: 2 SubTests: - name: test_1a status: PASS duration: 22 return_code: 0 error: . . . - name: test_26 status: PASS duration: 54 return_code: 0 error: duration: 2173 status: FAIL </pre> </div></div> <p>So despite all the tests passing, the test was marked failed in the results file, not sure why. I've updated the ticket's component to autotest, though I'm not sure it was AT's issue either, I just know it's further upstream than maloo</p> <p>We will pull this ticket into the next sprint to complete analysis to determine how often this happening and prioritize the effort to fix.</p> <p>The lustre test framework is responsible for the results.yml file. It might be a correct failure as there was a failure in cleaning up the ost-pools test:</p> <p>06:55:47:Starting test test_complete in suite ost-pools timeout at 1441094147<br/> 06:55:47:== ost-pools test complete, duration 2160 sec == 06:55:40 (1441090540)<br/> 06:55:47:CMD: shadow-35vm3 lctl pool_list lustre<br/> 06:55:47:Pools from lustre:<br/> 06:55:47:rm: cannot remove `/mnt/lustre/d405.sanity-hsm/striped_dir': Directory not empty<br/> 06:55:47:rm: cannot remove `/mnt/lustre/d500.sanity-hsm': Directory not empty<br/> 06:55:47: ost-pools : @@@@@@ FAIL: remove sub-test dirs failed <br/> 06:55:47: Trace dump:<br/> 06:55:47: = /usr/lib64/lustre/tests/test-framework.sh:4748:error_noexit()<br/> 06:55:47: = /usr/lib64/lustre/tests/test-framework.sh:4779:error()<br/> 06:55:47: = /usr/lib64/lustre/tests/test-framework.sh:4293:check_and_cleanup_lustre()<br/> 06:55:47: = /usr/lib64/lustre/tests/ost-pools.sh:1574:main()<br/> 06:55:47:Dumping lctl log to /logdir/test_logs/2015-09-01/lustre-ppc-el6_6-x86_64-vs-lustre-ppc-el6_6-x86_64_ppc64-<del>review-dne-part-2</del>-1_2_1_<em>191</em>_-70079184457860-005147/ost-pools..*.1441090543.log<br/> 06:55:47:CMD: shadow-31.shadow.whamcloud.com,shadow-35vm2,shadow-35vm3,shadow-35vm4,shadow-35vm5,shadow-35vm6,shadow-35vm7 /usr/sbin/lctl dk &gt; /logdir/test_logs/2015-09-01/lustre-ppc-el6_6-x86_64-vs-lustre-ppc-el6_6-x86_64_ppc64-<del>review-dne-part-2</del>-1_2_1_<em>191</em>_-70079184457860-005147/ost-pools..debug_log.\$(hostname -s).1441090543.log;<br/> 06:55:47: dmesg &gt; /logdir/test_logs/2015-09-01/lustre-ppc-el6_6-x86_64-vs-lustre-ppc-el6_6-x86_64_ppc64-<del>review-dne-part-2</del>-1_2_1_<em>191</em>_-70079184457860-005147/ost-pools..dmesg.\$(hostname -s).1441090543.log<br/> 06:55:59:ost-pools returned 0</p> <p>Okay. I'll check the script and error and will eventually convert the ticket into an LU or LDEV ticket.</p> <p>I've just run into this here:<br/> <a href="https://testing.hpdd.intel.com/test_sets/0273cf04-6d4e-11e5-bf10-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/0273cf04-6d4e-11e5-bf10-5254006e85c2</a></p> <p>For ppc test and example Nathaniel presented, auster returns 0 for all subtests, but clean-up fails at the end of the test suite.<br/> Although all information are there, it's cumbersome to dig into the suite log/stdout files for these events.<br/> It's not sure whether the situation has (should) to be handled in autotest. I think it's a problem in the Lustre test suite which should add 'test' (name == 'cleanup') that could pass, fail or timeout. I'll discuss the problem with Charlie.</p> <p>The problem is that 'lnet-selftest' in case of <a href="https://testing.hpdd.intel.com/test_sets/0273cf04-6d4e-11e5-bf10-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/0273cf04-6d4e-11e5-bf10-5254006e85c2</a> and<br/> 'ost-pools' for session <a href="https://testing.hpdd.intel.com/test_sets/bfdb5482-508d-11e5-95a9-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/bfdb5482-508d-11e5-95a9-5254006e85c2</a> contain clean-up code that will<br/> cause auster to fail (aka exit with status != 0) if an operation fails. These clean-up commands should be bundled in a test (cleanup would <br/> be a good name) that could FAIL|TIMEOUT|PASS|SKIP. This would make the failure immediately transparent to any user. Otherwise<br/> the clean-up acts like a 'hidden' test for the suite.<br/> We think this is a design flaw of the Lustre test suites especially those mentioned explicitly in the ticket and should be solved within the Lustre<br/> (internal) test framework.</p> <p>+1 on master <a href="https://testing.hpdd.intel.com/test_sets/e897ff26-0c90-11e8-a6ad-52540065bddc" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/e897ff26-0c90-11e8-a6ad-52540065bddc</a></p> Development Rank 1|hzxmbj: Rank (Obsolete) 9223372036854775807 Severity Story Points 0.5