Jakob Unterwurzacher 9768376bd1 tests: add TestXfs124 ...

This test reproduces the problem xfstests generic/124 uncovered.
The warning itself is harmless, but we should either (1) add locking
so that this cannot happen anymore or (2) drop the warning.

Currently fails:

$ go test -v
=== RUN   Test1980Tar
--- PASS: Test1980Tar (0.00s)
=== RUN   TestCtlSock
--- PASS: TestCtlSock (0.10s)
=== RUN   TestOpenTruncateRead
--- PASS: TestOpenTruncateRead (0.00s)
=== RUN   TestWORead
--- PASS: TestWORead (0.00s)
=== RUN   TestXfs124
cipherSize 18 == header size: interrupted write?
-wpanic turns this warning into a panic: cipherSize 18 == header size: interrupted write?

2017-05-01 18:44:03 +02:00

..

cli

Check for trailing garbage after the password

2017-02-12 17:59:09 +01:00

defaults

tests: add TestXfs124

2017-05-01 18:44:03 +02:00

example_filesystems

cli: enable "-raw64" by default

2017-03-07 20:56:50 +01:00

hkdf_sanity

tests: add hkdf_sanity tests with broken example filesystem

2017-03-18 16:48:58 +01:00

matrix

Drop Go 1.4 compatability code everywhere

2017-03-05 17:44:14 +01:00

plaintextnames

Fix misspellings

2016-10-24 19:18:13 +02:00

reverse

tests: reverse: don't run tests that ignore "-plaintextnames" twice

2017-03-07 20:53:58 +01:00

stress_tests

Get rid of remaining $GOPATH dependencies

2017-02-20 21:26:42 +01:00

test_helpers

tests: get rid of syscall.PathMax

2017-02-16 18:47:04 +01:00

canonical-benchmarks.bash

benchmark: add md5sum read performance benchmark

2017-03-18 16:23:33 +01:00

dl-linux-tarball.bash

tests: OSX compat: use OSX-style "stat -f"

2017-02-16 19:10:36 +01:00

fuse-unmount.bash

OSX compat: replace fusermount calls with fuse-unmount.bash

2017-02-15 23:02:01 +01:00

maxlen.bash

maxlen.bash: result was 1 too high

2016-10-04 10:26:22 +02:00