gocryptfs/tests/test_helpers, branch v1.7.1Mirror of gocryptfs source code on Githubhttp://nuetzlich.net/cgit/gocryptfs/atom?h=v1.7.12019-10-06T19:53:20+00:00tests: use /var/tmp by default2019-10-06T19:53:20+00:00Jakob Unterwurzacher2019-10-06T19:50:27+00:00urn:sha1:8c4429408716d9890a98a48c246d616dbfea7e31
On Fedora, /tmp is tmpfs, which behaves differently than ext4
(inode numbers are never reused, for example).
Use /var/tmp, which is ext4 on Fedora, to get a more realistic
test environment.
This also allows us to drop the xattr workaround.
tests: filter leaked fds by prefix2019-10-06T17:37:51+00:00Jakob Unterwurzacher2019-10-06T17:04:16+00:00urn:sha1:1fb18f4a9ef2bbbc6e7c774fa064808a3952bb3f
When running
$ go test ./tests/matrix/
in isolation, it failed like this:
fd leak? before, after:
[0r=/dev/null 3w=/dev/null 5r=/proc/8078/fd (hidden:4)]
[0r=/dev/null 3w=/dev/null 5w=/tmp/go-build366655199/b001/testlog.txt 7r=/proc/8078/fd (hidden:4)]
Filter by prefix to get rid of this spurious test failure.
tests: clarify which process seems to be leaking fds2019-10-06T16:48:09+00:00Jakob Unterwurzacher2019-10-06T16:48:09+00:00urn:sha1:d361f6e35bb97ef8f060131ea5b29f922e613c49
The tests check if they leak fds themselves, but we also
check if gocryptfs leaks fds. Clarify what is what in the
error message.
test_helpers: ListFds: handle an exited process gracefully2019-09-08T14:15:35+00:00Jakob Unterwurzacher2019-09-08T14:15:35+00:00urn:sha1:ea634090dce2f9a7fe62bae397b92d5940a0be0e
This used to dump a backtrace to the console which obscured what
is going on.
tests: fix root_test permission issues2019-05-01T16:29:06+00:00Jakob Unterwurzacher2019-05-01T16:29:06+00:00urn:sha1:e22c8ea0bd9b1670d4ab2bb4c810119f43f16f40
The parent directories need execute all permissions.
tests: split testParentDir by UID2019-05-01T11:12:44+00:00Jakob Unterwurzacher2019-05-01T11:06:52+00:00urn:sha1:3ac98722306c316223169fa4a0f9a2769bcceb65
When we run tests as root, they will leave root-owned files
in testParentDir, which causes trouble when we run tests as
a normal user later on. Split by UID.
test_helpers: better function comments for InitFS and Mount2019-05-01T11:12:44+00:00Jakob Unterwurzacher2019-05-01T10:47:54+00:00urn:sha1:41dfbe67f827ecaebd7dd81a079f38a676288800
It's confusing that you must pass "-extpass" for Mount but not
for InitFS. Note that in the comment.
tests: check that we can delete directories with all permission2019-01-20T13:32:59+00:00Jakob Unterwurzacher2019-01-20T13:32:59+00:00urn:sha1:ec4c9f2adb7bf1edde43a981dc690d3fee6175e8
Regression test for https://github.com/rfjakob/gocryptfs/issues/354
tests: Increase timeout in Mount() function.2019-01-15T21:08:20+00:00Sebastian Lackner2019-01-15T18:40:53+00:00urn:sha1:1d2ce9c213093c91b86ba6c28537ccda4469fe1f
This avoids sporadic test failures on macOS.
tests: reduce noise on MacOS2019-01-14T21:11:15+00:00Jakob Unterwurzacher2019-01-14T21:11:15+00:00urn:sha1:20140e24ed339ef97b4f3946da3b05f930898713
This should get rid of
Openat: O_NOFOLLOW missing: flags = 0x0
Fchmodat: adding missing AT_SYMLINK_NOFOLLOW flag
sys_common_test.go:203: chmod on symlink should have failed, but did not. New mode=0333
UnmountErr: "[...]/057376762.mnt" was not found in MountInfo, cannot check for FD leak
and add some context to
--- FAIL: TestUtimesNano (0.00s)
matrix_test.go:628: no such file or directory
See https://github.com/rfjakob/gocryptfs/pull/343#issuecomment-453888006
for full test output