summaryrefslogtreecommitdiff
path: root/yarns/0050-multiple-clients.yarn
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2014-03-06 21:27:17 +0000
committerLars Wirzenius <liw@liw.fi>2014-03-06 21:27:17 +0000
commite3c90808693fc6e75d5834863206512104c439e4 (patch)
tree5ba8969ae983b1fe9dd87abd7e660ce88d89a1d4 /yarns/0050-multiple-clients.yarn
parentb146da5d96d863434aa2fdf21d5521c8690489b6 (diff)
downloadobnam-e3c90808693fc6e75d5834863206512104c439e4.tar.gz
Add test for bug found recently
Diffstat (limited to 'yarns/0050-multiple-clients.yarn')
-rw-r--r--yarns/0050-multiple-clients.yarn16
1 files changed, 16 insertions, 0 deletions
diff --git a/yarns/0050-multiple-clients.yarn b/yarns/0050-multiple-clients.yarn
index 0cacd464..9119f034 100644
--- a/yarns/0050-multiple-clients.yarn
+++ b/yarns/0050-multiple-clients.yarn
@@ -53,3 +53,19 @@ existing client's name.
GIVEN directory L with interesting filesystem objects
WHEN user U1 backs up directory L to repository R
THEN user U2 can see user U1 in repository R
+
+Two clients sharing chunks, one forgets its generations
+-------------------------------------------------------
+
+What happens when two clients share chunks and one of them forgets its
+generations? A problem was found in this scenario by Nemo Inis in
+2014.
+
+ SCENARIO two clients share chunks and one forgets is generations
+ GIVEN 1k of new data in directory L
+ AND a manifest of L in M
+ WHEN user U1 backs up directory L to repository R
+ AND user U2 backs up directory L to repository R
+ AND user U1 forgets the oldest generation in repository R
+ AND user U2 restores their latest generation in repository R into X
+ THEN L, restored to X, matches manifest M