gocryptfs/tests/matrix, branch v2.0-beta1 Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=v2.0-beta1 2020-09-09T16:18:37+00:00 tests: add TestInoReuse 2020-09-09T16:18:37+00:00 Jakob Unterwurzacher 2020-09-09T16:18:37+00:00 urn:sha1:db61ec5115f6d2ae0e9dfcf2b87163221a969f6b v2api/reverse: implement Statfs 2020-08-16T17:41:00+00:00 Jakob Unterwurzacher 2020-08-16T17:41:00+00:00 urn:sha1:58a2726977a1b1f92063a1e51c0769af71833e72 test_helper: VerifyExistence: don't panic 2020-08-15T13:39:08+00:00 Jakob Unterwurzacher 2020-08-15T13:39:08+00:00 urn:sha1:f270135c1614843f43a9df0e68b6e3fa556b6774 Instead bubble up the error to the testing object. tests: TestMagicNames: add warmup rounds 2020-07-12T19:00:52+00:00 Jakob Unterwurzacher 2020-07-12T18:58:38+00:00 urn:sha1:d7db071528cff2450fd766bb48d0303444f18bf5 Chasing a bug that seems to have nothing to do with magic names, as it already triggers during warmup: --- FAIL: TestMagicNames (0.00s) matrix_test.go:773: Testing n="warmup1" matrix_test.go:773: Testing n="warmup2" matrix_test.go:820: no such file or directory v2api: Getattr: use file handle if passed 2020-07-12T13:08:17+00:00 Jakob Unterwurzacher 2020-07-12T13:08:17+00:00 urn:sha1:f11432d02ab8fce306ba85e735b7c3db085f9da6 Fix spelling mistakes found by misspell 2020-05-09T22:25:49+00:00 Jakob Unterwurzacher 2020-05-09T22:25:49+00:00 urn:sha1:ead7008a08f9ace4591ebbc03e63fdc7ef37e502 https://github.com/client9/misspell tests: use t.Name() 2020-05-09T13:42:57+00:00 Jakob Unterwurzacher 2020-05-09T13:42:57+00:00 urn:sha1:c19baa10f8e8365ed9e3212a003a6b8f31f0320a We did not use t.Name() as it was not available before Go 1.8. Now the oldest Go version we support is Go 1.11, so we can use it. tests: randomize data in testWriteN 2020-02-15T20:56:08+00:00 Jakob Unterwurzacher 2020-02-15T20:56:08+00:00 urn:sha1:6eca07e36e2e58ff7495305ed7cb0fdcc36436e6 Just writing zeros carries the risk of not detecting wrongly created file holes. Write random data instead. tests: filter leaked fds by prefix 2019-10-06T17:37:51+00:00 Jakob Unterwurzacher 2019-10-06T17:04:16+00:00 urn: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 fds 2019-10-06T16:48:09+00:00 Jakob Unterwurzacher 2019-10-06T16:48:09+00:00 urn: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.