diff options
| author | Jakob Unterwurzacher | 2023-06-09 14:35:04 +0200 |
|---|---|---|
| committer | Jakob Unterwurzacher | 2023-06-09 15:07:45 +0200 |
| commit | 751acc4698aa299624a593745d0daf82f5a4fe10 (patch) | |
| tree | 98c813a75300425f49b285d3996a2e1710e98a38 /internal/fusefrontend/file_lock.go | |
| parent | d8f4bdb72a1bcef509fd3e4258c96f8f67db8203 (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 'internal/fusefrontend/file_lock.go')
0 files changed, 0 insertions, 0 deletions