gocryptfs/tests/test_helpers, branch v1.1-beta1Mirror of gocryptfs source code on Githubhttp://nuetzlich.net/cgit/gocryptfs/atom?h=v1.1-beta12016-09-25T14:43:17+00:00tests: smarter error handling in ResetTmpDir2016-09-25T14:43:17+00:00Jakob Unterwurzacher2016-09-25T12:57:04+00:00urn:sha1:f8da264222f7348c6b9e6dd9d372200f850d2878
Look at the error code from os.Remove and decide about the
right thing to do.
Gets rid of spurious fusermount error messages.
reverse: add longname benchmark2016-09-25T14:43:17+00:00Jakob Unterwurzacher2016-09-24T20:45:25+00:00urn:sha1:6c52c1a6e6176ba7b6922ee27df7ddd09991b57etests: add verbose output when unmounting2016-07-11T18:41:53+00:00Jakob Unterwurzacher2016-07-11T18:40:53+00:00urn:sha1:df17f1d702bea709228b9923a8ed2fc19005ba43tests: use unmount wrapper in ResetTmpDir2016-07-11T18:41:16+00:00Jakob Unterwurzacher2016-07-11T18:31:36+00:00urn:sha1:1c54fcd04bbf274dd5d4300e433bdcb1bb32e1ce
This should make it work on OSX.
Also, split unmount into two functions. Depending on what you
want,
* UnmountErr returns the resulting error
* UnmountPanic panics if the error was not nil
tests: OSX: cast st.Blksize to int642016-07-04T06:22:05+00:00Jakob Unterwurzacher2016-07-04T06:20:52+00:00urn:sha1:9d17fdb2068a5217ffab260db671c1cc50536e04
On Linux, Blksize is already int64. But on OSX
it is int32 and that caused a compile failure.
https://github.com/rfjakob/gocryptfs/issues/15
tests: call umount instead of fusermount on OSX2016-07-02T18:06:20+00:00Jakob Unterwurzacher2016-07-02T18:06:20+00:00urn:sha1:d5b7eb33daec612626305c961b7ec6d5eccd79a7
Reported at https://github.com/rfjakob/gocryptfs/issues/15
fusefrontend: add fallocate support2016-07-02T17:52:09+00:00Jakob Unterwurzacher2016-07-02T17:43:57+00:00urn:sha1:54470baa23bf98adde69dc1a074c852ea19127d1
Mode=0 (default) and mode=1 (keep size) are supported.
The patch includes test cases and the whole thing passed xfstests.
Fixes https://github.com/rfjakob/gocryptfs/issues/1 .
test: split up integration_tests2016-06-29T22:57:14+00:00Jakob Unterwurzacher2016-06-29T22:57:14+00:00urn:sha1:02b6d3067d502bcc063965a5a9d75aa693125e1b
...into "matrix" and "normal".
Also:
* Make running multiple packages in parallel safe, see
http://stackoverflow.com/questions/23715302/go-how-to-run-tests-for-multiple-packages
* Don't depent on test_helper.TmpDir and friends to have a terminating slash
tests: give "-plaintextnames" its own test package2016-06-27T19:40:39+00:00Jakob Unterwurzacher2016-06-27T19:39:02+00:00urn:sha1:2720cd7b0d2711101b841c06e0068d5d3ae1b59e
...and add tests for checking that gocryptfs.diriv
does not get created.
The main "integration_tests" package has become quite
big and convoluted over time.
This small separate package should make writing tests
for "-plaintextnames" easier.
As seen in "fusefrontend: fix PlaintextNames versions of Mkdir, Rmdir",
we need more of them.
Drop deprecated "-diriv" option2016-06-23T19:38:59+00:00Jakob Unterwurzacher2016-06-23T19:29:00+00:00urn:sha1:b17f0465c7c38cab2f1f4ad0fc25d64d5cd175e7
The DirIV feature flag is already mandatory, dropping the command
line option is the final step.