-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Test Python
-
None
-
Storage Engines, Storage Engines - Foundations
-
SE Foundations - 2025-07-04
-
3
This ticket triages the following files that crash in C running the disagg hook:
- test_alter01.py
- test_alter02.py
- test_alter04.py
- test_alter05.py
- test_bug029.py
- test_bug030.py
- test_bug031.py
- test_bug033.py
- test_cc02.py
- test_cc09.py
- test_cc10.py
- test_checkpoint02.py
- test_checkpoint22.py
- test_checkpoint33.py
- test_checkpoint35.py
- test_checkpoint_snapshot02.py
- test_checkpoint_snapshot03.py
- test_config04.py
- test_cursor02.py
- test_cursor03.py
- test_cursor06.py
- test_cursor13.py
- test_durable_rollback_to_stable.py
- test_encrypt01.py
- test_encrypt04.py
- test_error_info02.py
- test_hs11.py
- test_import04.py
- test_prepare11.py
- test_prepare20.py
- test_prepare22.py
- test_prepare23.py
- test_prepare27.py
- test_prepare29.py
- test_prepare_hs02.py
- test_prepare_hs04.py
- test_reserve.py
- test_rollback_to_stable12.py
- test_rollback_to_stable13.py
- test_rollback_to_stable20.py
- test_rollback_to_stable22.py
- test_rollback_to_stable24.py
- test_rollback_to_stable31.py
- test_rollback_to_stable32.py
- test_rollback_to_stable37.py
- test_rollback_to_stable38.py
- test_rollback_to_stable39.py
- test_rollback_to_stable41.py
- test_rollback_to_stable44.py
- test_tiered16.py
- test_timestamp04.py
- test_timestamp26.py
- test_truncate05.py
- test_truncate11.py
- test_truncate12.py
- test_truncate19.py
- test_txn02.py
- test_txn09.py
- test_txn10.py
Each of these crashes in C, that is would give a core dump when running like this:
python3 ../test/suite/run.py -v 2 --hook disagg test_checkpoint10.py
These should be run in the debugger to see where they crash. It's likely that some have the same sorts of failures. Individual tickets should be created as indicated and assigned to teams. Part of the ticket should be to be one or both of: resolve the crash by fixing WT library (the library should generally not crash, although these may be asserts - the best result is to return an error to the caller) AND/OR modify the test so it is appropriate for disagg AND/OR skip the test for disagg.
Part of the work of individual tickets should also be remove the entry in test/suite/hook_disagg.fail . Even if the test is skipped.
If the list is too long for one ticket, some of it can be split out.
See WT-14680 for background.
- is related to
-
WT-14680 Disagg python testing: initial triage of (previously) failing tests
-
- Closed
-