The SortedDataInterface unit-test is broken for RocksDB, most likely because of this change, which now requires that SortedDataInterface::Cursor implementations for unique indexes never return duplicate keys.
This is the failure (obtained from the most recent evergreen run):
[cpp_unit_test:storage_rocks_index_test] 2015-11-18T05:45:04.237+0000 2015-11-18T05:45:04.236+0000 I - [main] SortedDataInterface | tests: 146 | fails: 2 | assert calls: 0 | time secs: 2.361
[cpp_unit_test:storage_rocks_index_test] 2015-11-18T05:45:04.237+0000 SaveAndRestorePositionUniqueIndexWontReturnDupKeys_Forward Expected cursor->next() == IndexKeyEntry(key2, loc2) ( { : 1 }@RecordId(44) == { : 2 }@RecordId(44)) @src/mongo/db/storage/sorted_data_interface_test_cursor_saverestore.cpp:458
[cpp_unit_test:storage_rocks_index_test] 2015-11-18T05:45:04.237+0000 SaveAndRestorePositionUniqueIndexWontReturnDupKeys_Reverse Expected cursor->next() == IndexKeyEntry(key3, loc1) ( { : 4 }@RecordId(42) == { : 3 }@RecordId(42)) @src/mongo/db/storage/sorted_data_interface_test_cursor_saverestore.cpp:537
[cpp_unit_test:storage_rocks_index_test] 2015-11-18T05:45:04.237+0000 2015-11-18T05:45:04.236+0000 I - [main] TOTALS | tests: 151 | fails: 2 | assert calls: 0 | time secs: 2.427
- is related to
-
SERVER-21403 $snapshot can return duplicates on 3.2 in the case of an MMAPv1 document move
-
- Closed
-