From 734e63a7b5f6030796d0c62f22b52cc2a5ddf32c Mon Sep 17 00:00:00 2001 From: Greg Farnum Date: Mon, 19 Sep 2011 10:45:27 -0700 Subject: [PATCH] locking: add another test. I used this to test the correctness of more wait lock behavior. Unfortunately it doesn't fail on the wrong behavior in question, but it does trigger it and will catch other sorts of issues (ie, locks hanging around incorrectly). --- collections/multiclient/tasks/locking2.yaml | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 collections/multiclient/tasks/locking2.yaml diff --git a/collections/multiclient/tasks/locking2.yaml b/collections/multiclient/tasks/locking2.yaml new file mode 100644 index 0000000000000..33f8a5229c2d2 --- /dev/null +++ b/collections/multiclient/tasks/locking2.yaml @@ -0,0 +1,10 @@ +kernel: +tasks: +- ceph: +- kclient: +- lockfile: [{client: client.0, lockfile: testfile, holdtime: 4, maxwait: 5, offset: 0, length: 5}, + {client: client.1, lockfile: testfile, holdtime: 4, maxwait: 5, offset: 10, length: 1}, + {client: client.1, lockfile: testfile, holdtime: 2, maxwait: 4, offset: 0, length: 15, expectfail: True}, + {client: client.1, lockfile: testfile, holdtime: 4, maxwait: 10, offset: 0, length: 15}, + 10, + {client: client.0, lockfile: testfile, holdtime: 3, maxwait: 4, offset: 0, length: 15}] -- 2.39.5