[LU-4880] conf-sanity test_32c: failed with 1 Created: 11/Apr/14  Updated: 09/Oct/21  Resolved: 09/Oct/21

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.4.3
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Maloo Assignee: WC Triage
Resolution: Cannot Reproduce Votes: 0
Labels: mn4

Severity: 3
Rank (Obsolete): 13502

 Description   

This issue was created by maloo for Bob Glossman <bob.glossman@intel.com>

This issue relates to the following test suite run: http://maloo.whamcloud.com/test_sets/fb844d20-c11b-11e3-a3ca-52540035b04c.

This looks a lot like LU-4223, but that is fixed. I think the fix is in b2_4, although the changes there look a lot less than the changes in master in the same area.

The sub-test test_32c failed with the following error:

test_32c failed with 1

Info required for matching: conf-sanity 32c



 Comments   
Comment by Bob Glossman (Inactive) [ 11/Apr/14 ]

maloo reports "Failure Rate: 53.00% of last 100 executions [all branches]"
I'm finding it hard to believe the rate is really that high.
searching in maloo does show a lot of recent instances in various branches.
some have been identified as LU-4223 even though that is marked fixed.

Comment by Bob Glossman (Inactive) [ 11/Apr/14 ]

retest of the same patch hit the same failure; http://review.whamcloud.com/#/c/9929
https://maloo.whamcloud.com/test_sets/e758f77a-c1bf-11e3-b1ce-52540035b04c

It's starting to seem likely that something in the patch is bad and causing this failure.

Comment by Di Wang [ 12/Apr/14 ]

Does 2.4 include http://review.whamcloud.com/#/c/8409/ and http://review.whamcloud.com/#/c/8409/. It seems the failure is because of this.

Comment by Bob Glossman (Inactive) [ 14/Apr/14 ]

As far as I can tell b2_4 doesn't include http://review.whamcloud.com/#/c/8409. Did you really mean to say #8409 twice, or was that a typo?

Comment by Bob Glossman (Inactive) [ 15/Apr/14 ]

back port of http://review.whamcloud.com/#/c/8409

http://review.whamcloud.com/9959

Generated at Sat Feb 10 01:46:39 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.