Whamcloud Community JIRA https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 [LU-14667] sanity test_27J: Timeout occurred after 102 mins, last suite running was sanity https://jira.whamcloud.com/browse/LU-14667 Lustre <p>This issue was created by maloo for Chris Horn &lt;hornc@cray.com&gt;</p> <p>This issue relates to the following test suite run: <a href="https://testing.whamcloud.com/test_sets/9324493f-fd08-4ddf-a0ca-114daef69104" class="external-link" target="_blank" rel="nofollow noopener">https://testing.whamcloud.com/test_sets/9324493f-fd08-4ddf-a0ca-114daef69104</a></p> <p>test_27J failed with the following error:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>Timeout occurred after 102 mins, last suite running was sanity </pre> </div></div> <p>Very similar to the other timeout issues. No apparent problem with the patch under test.</p> <p>VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV<br/> sanity test_27J - Timeout occurred after 102 mins, last suite running was sanity</p> LU-14667 sanity test_27J: Timeout occurred after 102 mins, last suite running was sanity Bug Minor Open Unresolved WC Triage Maloo Tue, 4 May 2021 18:15:56 +0000 Thu, 28 Apr 2022 23:45:10 +0000 0 3 <p>This may have been caused by a hardware problem on the test node (ARM), which AFAIK is known to be a bit flakey. The test logs look like an abrupt node halt, and then during reboot it continually dumps stacks in the core kernel:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>[ 2541.276200] Lustre: DEBUG MARKER: == sanity test 27J: basic ops on file with foreign LOV =============================================== 19:37:49 (1620070669) &lt;ConMan&gt; Console [onyx-24vm1] disconnected from &lt;onyx-24:6000&gt;. </pre> </div></div> <p>There haven't been any other failures in this particular test in many weeks, and definitely these patches don't seem related to the test that failed.</p> Related Development Rank 1|i01tpz: Rank (Obsolete) 9223372036854775807 Severity