mick.graham@mongodb.com hit a snapshot-isolation mismatch failure in a patch build on develop with a release build.
It looks potentially to be truncate related. The key thing to note here is that these are snapshot-isolation mismatches, not mirror checking mismatches The error:
[2023/08/16 08:40:05.035] table:T00002: WiredTiger trace ID: 3
[2023/08/16 08:40:05.035] snapshot-isolation 4206305 search mismatch
[2023/08/16 08:40:05.035] table:T00002: WiredTiger trace ID: 3
[2023/08/16 08:40:05.035] snapshot-isolation 4206306 search mismatch
[2023/08/16 08:40:05.035] expected {DUPLICATEV/LMNOPQRSTUVWXYZ}
[2023/08/16 08:40:05.035] found {deleted}
[2023/08/16 08:40:05.035] table:T00002: WiredTiger trace ID: 3
[2023/08/16 08:40:05.035] snapshot-isolation 4206308 search mismatch
[2023/08/16 08:40:05.035] expected {DUPLICATEV/LMNOPQRSTUVWXYZ}
[2023/08/16 08:40:05.035] found {deleted}
[2023/08/16 08:40:05.035] snapshot-isolation 4206311 search mismatch
[2023/08/16 08:40:05.035] expected {DUPLICATEV/LMNOPQRSTUVWXYZ}
[2023/08/16 08:40:05.035] found {deleted}
- fixes
-
WT-17953 failed: format-stress-test-no-barrier on ubuntu2004-stress-tests-arm64 [wiredtiger-mongo-v7.0 @ 90351906] search data mismatch
-
- Closed
-