[LU-1003] Test failure on test suite parallel-scale

• Status: Resolved
• Project: Lustre
• Type: Bug
• Priority: Minor
• Reporter: Maloo
• Assignee: WC Triage
• Resolution: Cannot Reproduce
• Severity: 3

Description

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

This issue relates to the following test suite run: https://maloo.whamcloud.com/test_sets/927aca8c-3f51-11e1-990e-5254004bbbd3.

Usually metabench doesn't take so much time.

Comments

[Minh Diep]

In https://maloo.whamcloud.com/test_logs/9349033e-3f51-11e1-990e-5254004bbbd3/show_text
I found a timed out message from autotest, but the test continue to metabench

21:30:00:delete kernel-2 in 119.98 seconds
21:31:54:delete kernel-3 in 114.44 seconds
21:33:55:delete kernel-1 in 115.54 seconds
21:34:56:********** Timeout by autotest system **********21:35:49:delete kernel-0 in 115.18 seconds
21:35:49:
21:35:49:run complete:
21:35:49:==========================================================================
21:35:49:intial create total runs 4 avg 1.51 MB/s (user 1.93s sys 26.05s)
21:35:49:no runs for create
21:35:49:no runs for patch
21:35:49:compile total runs 4 avg 13.36 MB/s (user 0.46s sys 6.63s)
21:35:49:no runs for clean
21:35:49:no runs for read tree
21:35:49:read compiled tree total runs 3 avg 1.38 MB/s (user 3.44s sys 60.23s)
21:35:49:no runs for delete tree
21:35:49:delete compiled tree total runs 4 avg 116.29 seconds (user 1.51s sys 21.69s)
21:35:49:no runs for stat tree
21:35:49:no runs for stat compiled tree
21:35:49:Resetting fail_loc on all nodes...done.
21:35:49:PASS compilebench (3657s)
21:35:49:
21:35:49:== parallel-scale test metabench: metabench == 21:35:45 (1326605745)
21:35:49:OPTIONS:

could this slowness due to the stacktrace was run while metabench was running?

[Andreas Dilger]

Close old ticket.