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-1791 Lustre <p>The sanity.sh test_224b() that was added for <a href="https://jira.whamcloud.com/browse/LU-1039" title="data corruption in check_set" class="issue-link" data-issue-key="LU-1039"><del>LU-1039</del></a> takes over 15 minutes to complete just that one subtest (e.g. <a href="https://maloo.whamcloud.com/sub_tests/3d7bc580-ef9c-11e1-bdf7-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/sub_tests/3d7bc580-ef9c-11e1-bdf7-52540035b04c</a>). This needs to be improved so that it doesn't waste so much testing time (3-4h or more each day for all of the test nodes).</p> <p>This appears to be because it is not timing out until AT max (900s) is hit.</p> <p>We need a patch to change this test to reduce AT_max just for this test so that the test can complete more quickly.</p> LU-1791

sanity.sh test_224b takes too long to run

Technical task LU-1039 Minor Resolved Fixed WC Triage Andreas Dilger Mon, 27 Aug 2012 17:53:17 +0000 Sat, 10 Mar 2018 08:25:11 +0000 Sat, 10 Mar 2018 08:25:11 +0000 Lustre 2.3.0 Lustre 2.4.0 0 1 <p>Shadow, the test you added in commit c9590221dc43dd5e7a7ede389f0a7d9cf566e5bf takes a very long time to run, 939s in one recent case. Could you please look at this test and find a way to speed it up, without removing the functionality? I think reducing AT_max on the OSS for just this test should be enough, but since you wrote the test I want to make sure that this will not avoid the problem that it was trying to trigger.</p> <p>Recent test runs are in the 3s range.</p> Related LU-614 Development Rank 1|hzvcun: Rank (Obsolete) 5674