-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Developer Productivity
-
None
-
Storage Engines, Storage Engines - Persistence
-
None
-
None
When a function within WiredTiger results in an error, it is currently hard to determine exactly from where the error came from. This is in stark contrast to languages such as Java, where the origin of an exception can be determined from the stack trace. We should implement a similar functionality in WiredTiger, in which we would keep a log of error codes processed by WT_ERR, WT_RET, and their variants, and display it if need be.
- is depended on by
-
WT-15520 Dump the error log after a failed test/suite test
-
- Open
-
-
WT-15521 Clear expected errors from the error log
-
- Open
-
-
WT-15522 Configure the error log from cmake & determine the default value
-
- Open
-
-
WT-15533 Create a gdb macro for dumping the error log
-
- Open
-
-
WT-15568 Add the ability to dump the error log without the connection object
-
- Closed
-
-
WT-15523 Consider inlining parts of the error log
-
- Open
-
-
WT-15547 Simplify paths when printing the error log
-
- Closed
-
- is duplicated by
-
WT-12730 Consider WT_RET and friends storing more error information
-
- Closed
-
- is fixed by
-
WT-15531 Fix error log handling in test_layered31
-
- Closed
-
- is related to
-
WT-15441 Fix __clayered_compare failure
-
- Closed
-
-
WT-15528 Ensure read-only page is loaded as clean page
-
- Closed
-
-
WT-15514 Disagg python testing: skip test_import*.py tests
-
- Closed
-
-
WT-15535 Ensure checkpoint cleanup doesn't mark any readonly btree dirty
-
- Closed
-
-
SERVER-111310 Dump any logged WiredTiger error messages on unexpected failures
-
- Closed
-
-
WT-15541 Improve error pinpoint
-
- Closed
-
- related to
-
WT-15645 Error log improvement follow-on work
-
- Open
-
-
WT-15103 Enable disagg python testing on Evergreen waterfall
-
- Closed
-
-
WT-15410 test/format (disagg.mode=leader) Delta chain validation failed
-
- Closed
-