summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2024-02-07 20:18:54 +0200
committerLars Wirzenius <liw@liw.fi>2024-02-07 20:18:54 +0200
commit66193fabc2dc78686797cf40298cabeeb740549d (patch)
tree2e1318ef8551ac8c7bcb740d646eb438ca1840e0
parent05af834f59082e19c74e77c3d0cd65949b02c8de (diff)
downloadobnam2-66193fabc2dc78686797cf40298cabeeb740549d.tar.gz
tests: disable some tests that don't succeed when run as root
Signed-off-by: Lars Wirzenius <liw@liw.fi> Sponsored-by: author
-rw-r--r--obnam.md22
1 files changed, 19 insertions, 3 deletions
diff --git a/obnam.md b/obnam.md
index f7c0bbe..c4122c2 100644
--- a/obnam.md
+++ b/obnam.md
@@ -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