[LU-16539] replay-dual test_32: Timeout occurred after x minutes, last suite running was replay-dual

• Type: Bug
• Resolution: Unresolved
• Priority: Minor
• Severity: 3
• Assignee: WC Triage
• Reporter: Maloo

Description

This issue was created by maloo for Timothy Day <[e-mail]>

This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/5ae4d92c-fc89-4e8c-bf83-4b09c9e7ead2

test_32 failed with the following error:

Timeout occurred after 132 minutes, last suite running was replay-dual

Test session details:
clients: https://build.whamcloud.com/job/lustre-reviews/92186 - 4.18.0-372.32.1.el8_6.x86_64
servers: https://build.whamcloud.com/job/lustre-reviews/92186 - 4.18.0-372.32.1.el8_lustre.x86_64

<<Please provide additional information about the failure here>>

Maloo auto-associated EX-6786 (this isn't community viewable, but I it put here for the benefit of those that can see it).

VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
replay-dual test_32 - Timeout occurred after 132 minutes, last suite running was replay-dual

Issue Links

• is related to: LU-15809 replay-dual test_29: timeout llog_verify_record() lustre-MDT0000-osp-MDT0001: record is too large: 0 > 32768