-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Engines - Foundations
-
None
-
None
In WT-16037 we add Python disagg base tests to code coverage tracking. While it's a good starting point to make code change report useful for disagg related changes, we should be able to extend coverage further by adding more Python disagg tests (e.g. Python disagg tests for leader mode, Python disagg tests for follower mode).
It's worth noting certain Python disagg tests (e.g. "test_timestamp26") run to failure using non-diagnostic build (where code coverage tasks run) right now. WT-16184 was filed to run disagg testing using non-diagnostic build and uncover other possible failures.
Outcome:
- More Python disagg tests are added to the code coverage tracking, and the generated coverage report shows coverage improvements for some modules and source files.