-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Test Format
-
Storage Engines
-
StorEng - 2025-03-14
When there are test/format failures, often the output shows thousands and thousands of lines of warning or informational messages about WT_ROLLBACK. These messages confuse the baron scripts extracting failure information and make it very difficult to find or see the real error message, which is often just one line.
The messages are all like this:
[1731438670:153072][21209:0x7f5fce6a9700], t, file:T00008.wt, WT_CURSOR.prev: [WT_VERB_DEFAULT][ERROR]: __wt_modify_reconstruct_from_upd_list, 436: Read-uncommitted readers do not support reconstructing a record with modifies.: WT_ROLLBACK: conflict between concurrent operations [1731438670:207627][21209:0x7f5fce6a9700], t, file:T00009.wt, WT_CURSOR.prev: [WT_VERB_DEFAULT][ERROR]: __wt_modify_reconstruct_from_upd_list, 436: Read-uncommitted readers do not support reconstructing a record with modifies.: WT_ROLLBACK: conflict between concurrent operations [1731438671:892535][21209:0x7f5fcd6a7700], t, file:T00009.wt, WT_CURSOR.next: [WT_VERB_DEFAULT][ERROR]: __wt_modify_reconstruct_from_upd_list, 436: Read-uncommitted readers do not support reconstructing a record with modifies.: WT_ROLLBACK: conflict between concurrent operations [1731438672:281056][21209:0x7f5fcdea8700], t, file:T00009.wt, WT_CURSOR.prev: [WT_VERB_DEFAULT][ERROR]: __wt_modify_reconstruct_from_upd_list, 436: Read-uncommitted readers do not support reconstructing a record with modifies.: WT_ROLLBACK: conflict between concurrent operations
The solution could be to:
- Consider removing the message.
- Consider having test/format's message handler ignore or discard the message.
- Consider having the evergreen scripts filter it out.
Definition of Done:
- Goal 1: Choose one from the above solutions after analysis.
- Goal 2: Document the analysis in this ticket.
- Goal 3: Implement the chosen solution.