I am trying to run schema_abort with tiered storage. It is failing because it cannot find the bucket directory it is creating:
./test_schema_abort -PT -T 5 -t 10 -h WT_TEST0
Running test command: ./test_schema_abort -PT -T 5 -t 10 -h WT_TEST0 Parent: compatibility: false, in-mem log sync: false, timestamp in use: true, tiered in use: true Parent: Create 5 threads; sleep 10 seconds CONFIG: test_schema_abort -PT -h WT_TEST0 -T 5 -t 10 -PSD13360246,E10734556 [1677702419:695214][2290:0x7ff84f136680], connection: [WT_VERB_EXTENSION][ERROR]: dir_store: No such file or directory: bucket: bucket directory test_schema_abort: FAILED: void testutil_wiredtiger_open(TEST_OPTS *, const char *, const char *, WT_EVENT_HANDLER *, WT_CONNECTION **, _Bool, _Bool)/560: wiredtiger_open(home, event_handler, buf, connectionp): No such file or directory test_schema_abort: process aborting
If I do an ls -R of WT_TEST0 it does show a bucket directory.
schema_abort 250 >> ls -R WT_TEST0 WT_HOME/ bucket/ records/ WT_TEST0/WT_HOME: WiredTiger WiredTiger.lock WT_TEST0/bucket: WT_TEST0/records:
It seems like there is some chdir issues and relative pathnames that are broken.