diff options
| -rw-r--r-- | obnam.md | 22 |
1 files changed, 19 insertions, 3 deletions
@@ -1777,8 +1777,12 @@ given a manifest of the directory live restored in rest in rest.yaml then manifests live.yaml and rest.yaml match ~~~ -## Unreadable file +## FIXME: Unreadable file +FIXME: This scenario has been disabled, temporarily, as my current CI +system runs things as `root` and that means this scenario fails. + +~~~~~~~~ This scenario verifies that Obnam will back up all files of live data, even if one of them is unreadable. By inference, we assume this means other errors on individual files also won't end the backup @@ -1797,9 +1801,14 @@ when I invoke obnam restore <GEN> rest then file live/data.dat is restored to rest then file live/bad.dat is not restored to rest ~~~ +~~~~~~~~ + +## FIXME: Unreadable directory -## Unreadable directory +FIXME: This scenario has been disabled, temporarily, as my current CI +system runs things as `root` and that means this scenario fails. +~~~~~~~~ This scenario verifies that Obnam will skip a file in a directory it can't read. Obnam should warn about that, but not give an error. @@ -1815,9 +1824,14 @@ when I invoke obnam restore <GEN> rest then file live/unreadable is restored to rest then file live/unreadable/data.dat is not restored to rest ~~~ +~~~~~~~~ -## Unexecutable directory +## FIXME: Unexecutable directory +FIXME: This scenario has been disabled, temporarily, as my current CI +system runs things as `root` and that means this scenario fails. + +~~~~~~~ This scenario verifies that Obnam will skip a file in a directory it can't read. Obnam should warn about that, but not give an error. @@ -1833,6 +1847,8 @@ when I invoke obnam restore <GEN> rest then file live/dir is restored to rest then file live/dir/data.dat is not restored to rest ~~~ +~~~~~~~ + ## Restore latest generation |