Feature #1214
closedqa: flock/fnctl lock tests
0%
Updated by Sage Weil almost 13 years ago
- Translation missing: en.field_position set to 708
Updated by Sage Weil almost 13 years ago
- Translation missing: en.field_story_points set to 5
- Translation missing: en.field_position deleted (
714) - Translation missing: en.field_position set to 714
Updated by Greg Farnum almost 13 years ago
- Status changed from New to In Progress
- Assignee set to Greg Farnum
I'll do this since I wrote most of the code, and the xfstests changes I made when writing it might be useful here.
Updated by Greg Farnum almost 13 years ago
Have initial commit of locktest task in teuthology. Still remaining: figuring out how to expand it to test stuff like wait locking, which the current code is just not architected for.
Updated by Greg Farnum almost 13 years ago
Okay, having looked into my previous modifications, they just needed a bit of clean up. I gave them some, and wrote a couple more tests for wait locking. It appears to work now!
Updated by Greg Farnum almost 13 years ago
- Status changed from In Progress to Resolved
Updated by Sage Weil almost 13 years ago
Does this include something like:
A: start process to take lock
B: start process to try to take lock, block
B: kill waiting process
A: release lock (kill process)
B: start new process to take lock
-> verify it succeeds.
This was the bug scale was seeing a couple weeks back.
Updated by Greg Farnum almost 13 years ago
- Status changed from Resolved to In Progress
Not right now -- I guess I can whip up an executable and a teuthology task for it.
Updated by Greg Farnum almost 13 years ago
- Status changed from In Progress to Resolved
The extra bits will be tracked in #1314