diff options
| author | Jakob Unterwurzacher | 2023-06-09 14:35:04 +0200 |
|---|---|---|
| committer | Jakob Unterwurzacher | 2024-12-04 19:53:15 +0100 |
| commit | a24e45b63167c255ab7db51a7b5097191085c826 (patch) | |
| tree | 86d728777ae89d2453a107634845a11511e4986b /contrib/mount-ext4-ramdisk.sh | |
| parent | 504dbe9f2df8ed0e136bd60539226f7ab6fc7e41 (diff) | |
tests/cluster: enable TestClusterConcurrentRW per default
Add the -sharedstorage flag to the mounts and make it more
severe by adjusting the I/O and file sizes to arbitrary unaligned
values.
It passes *most of the time*.
If it fails, it's like this, and the reason is that there is no
fcntl locks in the READ path yet.
gocryptfs/tests/cluster$ go test -run TestClusterConcurrentRW -v
=== RUN TestClusterConcurrentRW
doRead 2895433: corrupt block #0: cipher: message authentication failed
doRead 2895433: corrupt block #0: cipher: message authentication failed
doRead 2895433: corrupt block #0: cipher: message authentication failed
cluster_test.go:98: readThread iteration 9165: ReadAt failed: read /var/tmp/gocryptfs-test-parent-1026/3021427391/TestClusterConcurrentRW.366469887.mnt1/foo: input/output error
--- FAIL: TestClusterConcurrentRW (0.40s)
FAIL
exit status 1
FAIL github.com/rfjakob/gocryptfs/v2/tests/cluster 0.406s
Diffstat (limited to 'contrib/mount-ext4-ramdisk.sh')
0 files changed, 0 insertions, 0 deletions