[LU-1583] Test failure on test suite sanity Created: 29/Jun/12 Updated: 29/May/17 Resolved: 29/May/17 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Maloo | Assignee: | WC Triage |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Severity: | 3 |
| Rank (Obsolete): | 10437 |
| Description |
|
This issue was created by maloo for Chris Gearing <chris@whamcloud.com> This issue relates to the following test suite run: https://maloo.whamcloud.com/test_sets/e9b098ac-c17b-11e1-be99-52540035b04c. I need to provide some extra information here. This test was run as part of my developement for upgrade testing. This means that this session with b1_8 https://maloo.whamcloud.com/test_sessions/7408d5dc-c15e-11e1-9055-52540035b04c was run then this session https://maloo.whamcloud.com/test_sessions/e4613ca8-c17b-11e1-be99-52540035b04c then this session https://maloo.whamcloud.com/test_sessions/0ccd79e8-c1a6-11e1-b08c-52540035b04c My test is still under developement and will go live in autotest soon, bit I felt this issue here was worth raising for some investigation. |
| Comments |
| Comment by Jodi Levi (Inactive) [ 05/Jul/12 ] |
|
ASsign this back to Triage once you have implemented the workaround in |
| Comment by Andreas Dilger [ 29/May/17 ] |
|
Close old ticket. |