Details
-
Bug
-
Resolution: Duplicate
-
Minor
-
None
-
None
-
None
-
3
-
14708
Description
This issue was created by maloo for Bob Glossman <bob.glossman@intel.com>
This issue relates to the following test suite run: https://testing.hpdd.intel.com/test_sets/b39559ca-fe8b-11e3-a668-5254006e85c2.
maloo search shows only a couple of recent instances of this failure. The other is https://testing.hpdd.intel.com/test_sets/38525c26-fe87-11e3-a668-5254006e85c2. Very different mods being tested which makes me guess the failure isn't related to the patch under test.
Both instances happened on the same day, 6/28. Makes me suspicious that a recent master landing may be causing this to start happening suddenly.
The sub-test test_10a failed with the following error:
test failed to respond and timed out
Info required for matching: sanity-scrub 10a
Attachments
Issue Links
- duplicates
-
LU-4971 sanity-scrub test_2: ldlm_lock2desc()) ASSERTION( lock->l_policy_data.l_inodebits.bits == (MDS_INODELOCK_LOOKUP | MDS_INODELOCK_UPDATE | MDS_INODELOCK_LAYOUT)failed
- Resolved