-
Type:
Build Failure
-
Resolution: Gone away
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Not Applicable
checkpoint-filetypes-predictable-test on amazon2023-stress-tests-armv9
Host: i-00e1f352771f6f59c
Project: wiredtiger
Commit: 4acdaa42
Please refer to BF(G) Playbook for instructions on handling BF and BFG tickets as well as Auto-Resolution Rules
Task Logs:
checkpoint-filetypes-predictable-test task_log
Logs:
[1756437241:897973][6891:0xffffae306040], wiredtiger_open: [WT_VERB_DEFAULT][ERROR]: __posix_open_file, 893: RUNDIR_0/WiredTiger.lock: handle-open: open: No such file or directory [1756437241:898023][6891:0xffffae306040], wiredtiger_open: [WT_VERB_DEFAULT][ERROR]: __posix_open_file, 893: RUNDIR_0/WiredTiger: handle-open: open: No such file or directory [1756437241:898032][6891:0xffffae306040], wiredtiger_open: [WT_VERB_DEFAULT][ERROR]: __conn_single, 2027: The database directory is empty or needs recovery, cannot continue with a read only connection: Invalid argument RUNDIR_1: [1756437278:193966][6965:0xffffae912040], wt, wiredtiger_open: [WT_VERB_DEFAULT][ERROR]: __posix_open_file, 893: RUNDIR_1/WiredTiger.lock: handle-open: open: No such file or directory wt: WT_TRY_SALVAGE: database corruption detected Note: this issue typically arises from running wt util in an incorrect directory or not specifying one. Ensure you execute wt within a WiredTiger directory, or use the -h flag to direct it to one. RUNDIR_2: [1756437278:221759][6969:0xffff864c7040], wt, wiredtiger_open: [WT_VERB_DEFAULT][ERROR]: __posix_open_file, 893: RUNDIR_2/WiredTiger.lock: handle-open: open: No such file or directory wt: WT_TRY_SALVAGE: database corruption detected Note: this issue typically arises from running wt util in an incorrect directory or not specifying one. Ensure you execute wt within a WiredTiger directory, or use the -h flag to direct it to one.