summaryrefslogtreecommitdiff
path: root/Test.hs
Commit message (Collapse)AuthorAge
* test case for a40e203f23a87bbc6d362d33734f1e4dcf645871Gravatar Joey Hess2013-10-16
|
* tighten file2key to not produce invalid keys with no keyNameGravatar Joey Hess2013-10-16
| | | | | | A file named "foo-" or "foo-bar" was taken as a key's file, with a backend of "foo", and an empty keyName. This led to various problems, especially because converting that key back to a file did not yeild the same filename.
* quickcheck durationGravatar Joey Hess2013-10-08
|
* quickcheck schedule parsingGravatar Joey Hess2013-10-07
| | | | soo many arbitrary instances, so little time!
* ensure that hash representations don't change in futureGravatar Joey Hess2013-10-01
|
* more win warning squashingGravatar Joey Hess2013-09-06
|
* fix windows build warningGravatar Joey Hess2013-09-06
|
* fix warning in windows buildGravatar Joey Hess2013-09-06
|
* rename constructor for clariyGravatar Joey Hess2013-09-05
|
* wordingGravatar Joey Hess2013-09-04
|
* replace an over-explained Bool with a data typeGravatar Joey Hess2013-09-04
| | | | | This also highlights several places where a Read/Show or similar for the new data type could avoid redundant strings.
* Merge branch 'master' into encryptionGravatar Joey Hess2013-09-04
|\
* | Allow public-key encryption of file content.Gravatar guilhem2013-09-03
| | | | | | | | | | | | | | | | | | | | | | | | With the initremote parameters "encryption=pubkey keyid=788A3F4C". /!\ Adding or removing a key has NO effect on files that have already been copied to the remote. Hence using keyid+= and keyid-= with such remotes should be used with care, and make little sense unless the point is to replace a (sub-)key by another. /!\ Also, a test case has been added to ensure that the cipher and file contents are encrypted as specified by the chosen encryption scheme.
| * refactor git-annex branch log filename code into central locationGravatar Joey Hess2013-08-29
| | | | | | | | | | | | | | Having one module that knows about all the filenames used on the branch allows working back from an arbitrary filename to enough information about it to implement dropping dead remotes and doing other log file compacting as part of a forget transition.
* | Allow revocation of OpenPGP keys.Gravatar guilhem2013-08-29
|/ | | | | | | | | | | | | | | | | | | | | | | /!\ It is to be noted that revoking a key does NOT necessarily prevent the owner of its private part from accessing data on the remote /!\ The only sound use of `keyid-=` is probably to replace a (sub-)key by another, where the private part of both is owned by the same person/entity: git annex enableremote myremote keyid-=2512E3C7 keyid+=788A3F4C Reference: http://git-annex.branchable.com/bugs/Using_a_revoked_GPG_key/ * Other change introduced by this patch: New keys now need to be added with option `keyid+=`, and the scheme specified (upon initremote only) with `encryption=`. The motivation for this change is to open for new schemes, e.g., strict asymmetric encryption. git annex initremote myremote encryption=hybrid keyid=2512E3C7 git annex enableremote myremote keyid+=788A3F4C
* Unused: bugfixGravatar guilhem2013-08-26
| | | | Detect staged files that are not in the working tree.
* add test case for unused with unstaged linkGravatar Joey Hess2013-08-22
|
* enable 2 more tests on WindowsGravatar Joey Hess2013-08-04
|
* Windows: Fixed permissions problem that prevented removing files from ↵Gravatar Joey Hess2013-08-04
| | | | | | directory special remote. Directory special remotes now fully usable.
* missed some __WINDOWS__ definesGravatar Joey Hess2013-08-04
|
* regression test for 043672e11448516b70c0bea789f94fd3d5e16910Gravatar Joey Hess2013-07-30
|
* Improve test suite on Windows; now tests git annex sync.Gravatar Joey Hess2013-07-30
|
* update test suite for dropunused behavior changeGravatar Joey Hess2013-07-30
|
* Support unannex and uninit in direct mode.Gravatar Joey Hess2013-07-22
| | | | | | | | | | | | | | | | | | | In direct mode, it's best to whenever possible not move direct mode files out of the way, and so I made unannex avoid touching the direct mode file at all. That actually turns out to be easy, because in direct mode, unlike indirect mode, the pre-commit hook won't get confused if the unannexed file later gets added back by git add. So there's no need to commit the unannex right away; it can be staged for the user to commit later. This also means that unannex in direct mode is a lot faster than in indirect mode! Another subtle bit is the bookkeeping that is done when unannexing a direct mode file. The inode cache needs to be removed so that when uninit runs getKeysPresent, it doesn't see the cache and think the key is still present and crash when it's not. This commit is sponsored by Douglas Butts. Thanks!
* adjust test suite for changed dropunused behavior with bogus numbersGravatar Joey Hess2013-07-09
|
* few final bits for fully working test suite on windowsGravatar Joey Hess2013-06-18
|
* Windows: The test suite now passes on Windows (a few broken parts are disabled).Gravatar Joey Hess2013-06-18
| | | | | | | | | | | Better to have a working test suite that doesn't test a few things than no working test suite. Most of the disabled stuff is because for some reason "git annex sync" doesn't work when run inside the test suite. Looks like PATH problems. The directory and rsync special remotes seem broken on Windows, or maybe the tests are. Pretty sure the hook special remote test is broken.
* disable a test that windows git doesn't supportGravatar Joey Hess2013-06-18
|
* more slash fixesGravatar Joey Hess2013-06-18
|
* couple path separator fixesGravatar Joey Hess2013-06-18
|
* allow test temp dir removal to fail (working around some problem on Windows)Gravatar Joey Hess2013-06-18
|
* some basic tests of preferred content expressions and standard groupsGravatar Joey Hess2013-05-25
|
* Fix bug in parsing of parens in some preferred content expressions. This ↵Gravatar Joey Hess2013-05-24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | fixes the behavior of the manual mode group. The current manual mode preferred content expression is: "present and (((exclude=*/archive/* and exclude=archive/*) or (not (copies=archive:1 or copies=smallarchive:1))) or (not copies=semitrusted+:1))" The old matcher misparsed this, to basically: OR (present and (...)) (not copies=semitrusted+:1)) The paren handling and indeed the whole conversion from tokens to the matcher was just wrong. The new way may not be the cleverest, but I think it is correct, and you can see how it pattern matches structurally against the expressions when parsing them. That expression is now parsed to: MAnd (MOp <function>) (MOr (MOr (MAnd (MOp <function>) (MOp <function>)) (MNot (MOr (MOp <function>) (MOp <function>)))) (MNot (MOp <function>))) Which appears correct, and behaves correct in testing. Also threw in a simplifier, so the final generated Matcher has less unnecessary clutter in it. Mostly so that I could more easily read & confirm them. Also, added a simple test of the Matcher to the test suite. There is a small chance of badly formed preferred content expressions behaving differently than before due to this rewrite.
* add a test case for merge conflict automatic resolutionGravatar Joey Hess2013-05-20
|
* run the test suite twice, once in direct modeGravatar Joey Hess2013-05-20
| | | | | On a filesystem that only supports direct mode, it will test direct mode twice, but oh well.
* fix windows buildGravatar Joey Hess2013-05-19
|
* Allow building with gpg2.Gravatar Joey Hess2013-05-19
|
* better messageGravatar Joey Hess2013-05-17
|
* ssh warningsGravatar Joey Hess2013-05-17
|
* can't test gpg on Windows yetGravatar Joey Hess2013-05-17
|
* use posixcompatGravatar Joey Hess2013-05-17
|
* try building test suite on windowsGravatar Joey Hess2013-05-17
|
* fsck behavior varies in direct mode when the file is modifiedGravatar Joey Hess2013-05-17
|
* disable unused test in direct modeGravatar Joey Hess2013-05-17
| | | | | | | | | This test is actually pointing at a problem, with getKeysPresent in direct mode. When a file is git rm -f'd, this removes its content, but it's still listed by getKeysPresent. However, unused is fairly useless in direct mode, and the test needs to be updated to handle other differences, so disable it for now
* disable stuff that is not supported in direct modeGravatar Joey Hess2013-05-17
| | | | | Also fixed a git rm that failed due to seeing modified file content in direct mode.
* fix testGravatar Joey Hess2013-05-15
|
* cleanupGravatar Joey Hess2013-05-15
|
* more fixes for test suite in direct modeGravatar Joey Hess2013-05-15
| | | | Still quite a few failures.
* a few fixes for the test suite in direct modeGravatar Joey Hess2013-05-15
| | | | Still far from working.
* thread env through test suiteGravatar Joey Hess2013-05-15
| | | | | | | | This will allow porting it to Windows, which cannot set environment except when forking processes. This is nasty, but HUnit can only test the IO monad, so I cannot use a Reader monad.