-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
2
-
Storage Engines 2020-02-24
test/format running on margay-aws, http://build.wiredtiger.com:8080/job/wiredtiger-test-format-stress/73222/
failed with an assertion failure in the split code:
[1580710836:474026][31721:0x7f40f8c94700], t, file:wt.wt, WT_CURSOR.search: __split_parent, 705: alloc_refp - alloc_index->index == (ptrdiff_t)result_entries [1580710836:474060][31721:0x7f40f8c94700], t, file:wt.wt, WT_CURSOR.search: __wt_abort, 28: aborting WiredTiger library Aborted (core dumped)
The changes in develop since the last successful run are:
[WT-5489] The WT_REF_READING state is the same as WT_REF_LOCKING for the purposes of locking a WT_REF. (#5208) (commit: 8183f4c) (details / githubweb) WT-5393 prepared transaction rollback and API error handling fixes (#5105) (commit: 40b746e) (details / githubweb) WT-5488 Evergreen test/format jobs need to report the failing CONFIG (#5191) (commit: e1441ad) (details / githubweb) WT-5444 Added format tests in ppc buildvariant (#5190) (commit: 549a573) (details / githubweb) WT-5376 WT_UPDATE.type field can race with visibility checks when returning key/value pairs (#5173) (commit: 168c7f1) (details / githubweb)
- duplicates
-
WT-5518 Split-parent code can race with other threads when checking the WT_REF.state
- Closed