In output (see examples in WT-13985), we see the session name: WT_CURSOR.cbt->dhandle, which doesn't make sense. This is due to an error in the curfile_insert function, the line:
CURSOR_UPDATE_API_CALL_BTREE(cursor, session, ret, cbt->dhandle);
is incorrect, it should read
CURSOR_UPDATE_API_CALL_BTREE(cursor, session, ret, insert);
because the final arg should be the name of the function (not a dhandle), and it is used to construct a name that is temporarily given to the session during the API call.
- is related to
-
WT-14997 Disable layered tables on truncate tests
-
- Closed
-
-
WT-14999 Refactor __wt_update to use a union to store commit timestamps and rollback timestamps
-
- Closed
-
-
WT-13985 Did not run a sweep for 60 minutes in test_prepare_hs01 for CS
-
- Closed
-
-
WT-14987 Segfault in __wt_buf_grow_worker reading metadata file (RHEL8 zSeries unit-test)
-
- Closed
-
-
WT-14990 test_corrupt01.py fails when running runWT with disagg hook
-
- Closed
-
- related to
-
WT-14972 Fix FLCS cursor insert stalls or hangs for certain python tests
-
- Open
-
-
WT-14782 Disagg python testing: triage test_checkpoint*.py tests
-
- Closed
-
-
WT-14866 Change timewindow aggregation logic to aggregate prepare_ts
-
- Closed
-
-
WT-14969 Skip including a prepared update in the delta if it has been written
-
- Closed
-
-
WT-14970 Split prepare_ts and prepared_id into stop_prepare_ts, start_prepare_ts, stop_prepared_id, start_prepared_id
-
- Closed
-