Update StressTest to handle asynchronous write succeeding unexpectedly
As writing the file is done asynchronously, when the test doesn't wait for the write to complete but closes the file immediately, it is possible that the write succeeds. So updating the test to check that the result of reading the reopened file is either the original contents or the updated contents (i.e. the file was not corrupted). As the test succeeded locally before this change, tried with the file parameters to EXPECT_FILE_READ_EITHER() in both orders. Bug: 999421 Test: Updated test succeeds Change-Id: I7c9a3d948b3a93ccc878b28d1fd4f5bed5e1015c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1787590Reviewed-by:Xiaohan Wang <xhwang@chromium.org> Commit-Queue: John Rummell <jrummell@chromium.org> Cr-Commit-Position: refs/heads/master@{#694475}
Showing
Please register or sign in to comment