Revision 8e12638f3d0d91791cf06253493b8b15827f4b6c authored by sdong on 19 August 2019, 17:50:25 UTC, committed by Facebook Github Bot on 19 August 2019, 17:51:59 UTC
Summary: Atomic white box test's kill odd is the same as normal test. However, in the scenario that only WritableFileWriter::Append() is blacklisted, WritableFileWriter::Flush() dominates the killing odds. Normally, most of WritableFileWriter::Flush() are called in WAL writes, where every write triggers a WAL flush. In atomic test, WAL is disabled, so the kill happens less frequently than we antipated. In some rare cases, the kill didn't end up with happening (for reasons I still don't fully understand) and cause the stress test timeout. If WAL is disabled, make the odds 5x likely to trigger. Pull Request resolved: https://github.com/facebook/rocksdb/pull/5717 Test Plan: Run whitebox_crash_test_with_atomic_flush and whitebox_crash_test and observe the kill odds printed out. Differential Revision: D16897237 fbshipit-source-id: cbf5d96f6fc0e980523d0f1f94bf4e72cdb82d1c
1 parent e1c468d
| File | Mode | Size |
|---|---|---|
| env.cc | -rw-r--r-- | 12.6 KB |
| env_basic_test.cc | -rw-r--r-- | 12.6 KB |
| env_chroot.cc | -rw-r--r-- | 11.6 KB |
| env_chroot.h | -rw-r--r-- | 684 bytes |
| env_encryption.cc | -rw-r--r-- | 34.0 KB |
| env_hdfs.cc | -rw-r--r-- | 19.2 KB |
| env_posix.cc | -rw-r--r-- | 37.4 KB |
| env_test.cc | -rw-r--r-- | 57.2 KB |
| io_posix.cc | -rw-r--r-- | 32.9 KB |
| io_posix.h | -rw-r--r-- | 8.7 KB |
| mock_env.cc | -rw-r--r-- | 20.7 KB |
| mock_env.h | -rw-r--r-- | 4.2 KB |
| mock_env_test.cc | -rw-r--r-- | 2.7 KB |
Computing file changes ...
