Remove O_DIRECT from basic_read_test #114
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This test is failing sporadically in CI with corrupt data. I believe the cause is the same as why we reverted #84. Per the man page for
open(2)
,O_DIRECT
is not safe to use concurrently withfork
syscalls:Our test runner does a
fork
every time we mount a FUSE file system, since we don't run our tests as root, and so we need to execute thefusermount3
utility to do the mount. Since tests run concurrently, that means we will sometimes do one of these forks at the same time as this test is doing anO_DIRECT
read.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.