summaryrefslogtreecommitdiff
path: root/yarns/0030-basics.yarn
AgeCommit message (Collapse)AuthorFilesLines
2016-07-13Fix typos, from Andrea GelminiLars Wirzenius1-1/+1
2015-07-08Add missing restore step to test scenarioLars Wirzenius1-0/+1
2015-06-13Prevent restores to a non-empty --to directoryLars Wirzenius1-0/+25
2014-06-03Remove now-obsolete testLars Wirzenius1-20/+0
2014-04-11Don't allow backup root to be a symbolic linkLars Wirzenius1-0/+20
2014-04-08Bugfix: excluded files stayed in new generationLars Wirzenius1-0/+19
2014-03-27Convert unreadable-dir cmdtest to yarnLars Wirzenius1-0/+15
2014-03-27Convert unreadable-file cmdtest to yarnLars Wirzenius1-0/+19
Doing this exposed a bug in yarn, which meant that the test needs a newer yarn to run. (Not yet released.)
2014-03-24Fix count of backed up filesLars Wirzenius1-5/+1
2014-03-21Fix test suite failures on TMPDIR without user xattrLars Wirzenius1-3/+5
Remove use of extended attributes from some tests. Make the remaining tests be conditional on whether extended attributes actually work in the temporary directory (in the user.* namespace).
2014-03-11Add yarn for no-op backupsLars Wirzenius1-0/+26
2014-02-06Make exclude-caches scenario clearer, robustLars Wirzenius1-12/+8
Originally, we would create L/wanted, then do a manifest, then create L/cache, then backup, restore, verify. This would sometimes fail, if the full-second timestamp of L would change when L/cache was created. So we (well, I) changed it so that we fiddled with the manifest just before making a backup, but this was weird and confusing and would still sometimes fail. This should now be much clearer and therefore more robust.
2014-01-26Fix file restore, add xattr value change testLars Wirzenius1-15/+29
The single file restore test had a bug, in that it was depending on various test steps to execute fast enough that the wall clock did not advance to the next second. This has been fixed by allowing manifests to be done on single files instead of just directories. Add a test for an extended attribute value changing, and that being the only change in the live data. The backup needs to notice that it has changed. This was intended to be the original change in this commit, but I ran into the test bug above, so I had to fix that too. I was too lazy to detangle the two sets of changes for commits.
2014-01-26Convert user-old-node-size test to yarnLars Wirzenius1-0/+19
2014-01-25Convert restores-single-file to a yarnLars Wirzenius1-0/+14
2014-01-25Convert remove-checkpoints into a yarnLars Wirzenius1-0/+12
2014-01-25Convert two-roots to a yarnLars Wirzenius1-0/+16
2014-01-25Convert pre-epoch-mtime to a yarnLars Wirzenius1-0/+14
2014-01-25Convert no-roots-from-old-gens into yarnLars Wirzenius1-0/+15
2014-01-24Convert --exclude-cache test to yarnLars Wirzenius1-0/+35
2014-01-12Add test for multiple clients sharing a repositoryLars Wirzenius1-9/+9
As part of this, make every repository operation step require an explicit client name. The v6 reference formats have a client name embedded that is the hostname of my laptop, so make those tests use that name. This fixes what would not have run previously on any system that isn't named havelock. Oops.
2014-01-11Add yarn test for pretend backupsLars Wirzenius1-7/+23
Remove cmdtest test for this. To make things clearer in the new test, also change all the steps that use a backup repository to have the user specify it explicitly.
2013-12-05Refactor: remove implicit live data directoryLars Wirzenius1-13/+13
It is just as, if not more, clear, and not much more tedious, to be explicit about this.
2013-12-05Move FUSE tests into new yarn setupLars Wirzenius1-6/+0
2013-12-05Yarn test interesting filesystem objectsLars Wirzenius1-0/+13
2013-12-05Start writing about non-basic filesystem objectsLars Wirzenius1-0/+27
2013-12-04Refactor IMPLEMENTS to remove couplingLars Wirzenius1-2/+6
2013-12-04Add test for backing up sparse filesLars Wirzenius1-0/+25
2013-12-04Add basic backup testLars Wirzenius1-0/+24