-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Storage Engines
-
2
-
v6.3, v6.0
mick.graham@mongodb.com I was able to reproduce the original failure from WT-10258 on kodkod-aws. Since WT-10258 is very involved in the truncate logging issue and I believe your original failure is different from that issue I am opening this new ticket.
Your original failure is at:
https://spruce.mongodb.com/task/wiredtiger_ubuntu2004_stress_tests_format_stress_test_2_patch_5fd7e267d45ad2cc1704c5c2e0c1f43823b699d0_6386ce1a3066155c912e1950_22_11_30_03_29_31/logs?execution=0&logtype=task
It is distinct from the truncate failure in WT-10258 by:
- The log has no operations recorded.
- The failing verify starts immediately after the bulk load completes.
It took a long time to reproduce as I've been rerunning this CONFIG for couple weeks debugging whatever failure hit.
- is duplicated by
-
WT-10283 test/format mirror data mismatch on ubuntu2004-stress-tests
- Closed
-
WT-10549 failed: format-stress-sanitizer-ppc-test-2 on rhel8-ppc [wiredtiger @ 339cc7ed]
- Closed
- is related to
-
WT-10258 Mirror mismatch in test format stress test 2
- Closed
- related to
-
WT-12431 table_verify_mirror fails with rows <= base_keyno
- Closed