Details
-
Bug
-
Resolution: Fixed
-
Blocker
-
Lustre 2.6.0
-
3
-
13220
Description
This issue was created by maloo for Nathaniel Clark <nathaniel.l.clark@intel.com>
This issue relates to the following test suite run:
http://maloo.whamcloud.com/test_sets/fb88e8cc-b161-11e3-a823-52540035b04c
https://maloo.whamcloud.com/test_sets/e1eb27ec-b178-11e3-9a4b-52540035b04c
The sub-test test_230c failed with the following error:
stat /mnt/lustre/d230c.sanity/f5 failed
Info required for matching: sanity 230c
Attachments
Issue Links
Activity
review-dne-part-1 on master:
https://maloo.whamcloud.com/test_sets/943f6a6c-d117-11e3-ae99-52540035b04c
https://maloo.whamcloud.com/test_sets/97c012a8-cc9a-11e3-bda1-52540035b04c
https://maloo.whamcloud.com/test_sets/1a74ec9e-ca81-11e3-9211-52540035b04c
https://maloo.whamcloud.com/test_sets/c05cca3c-c860-11e3-9a8f-52540035b04c
hmm, it seems all failures above happened before 9806 is landed. Could some one post link of failure. And I also check maloo, and did not find this problem in the recent run.
Patch landed to Master.
Nathaniel, are you able to confirm if this fixes LU-4835 as you suggested?
Thank you!
maloo is currently reporting a VERY high failure rate on this:
Failure Rate: 98.00% of last 100 executions [all branches]
suspect it's blocking a lot of tests.
another:
https://maloo.whamcloud.com/test_sets/c7acb7c6-b8b5-11e3-a578-52540035b04c
Di,
it does look like most of the failures in the past two weeks are actually from patches that were based on a commit before the change 9806 landing (which was on 04-01), in particular a bunch of LFSCK test runs and DLC test runs.
There was one test failure that looked similar in one of your own patches: http://review.whamcloud.com/10041
It might be that this patch is re-introducing the same bug, or it could be a different bug with the same failure symptoms. Probably better to open a new bug for the 10041 failure and close this one.