-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Test Csuite
-
Storage Engines
-
StorEng - 2025-03-28, StorEng - 2025-04-25, SE Persistence - 2025-05-09
-
5
I was running random_abort against a failed database home directory and I'm getting a message that it cannot create a SAVE directory. The path is wrong. I haven't dug into what function call this message is coming from but it should be fixed. I have an absolute path to the database directory.
The home directory was in my home dir and I was in a <some_path>/build/test/csuite/random_abort directory of a WiredTiger tree to run a verify on the database:
[sue@kodkod-aws (1) random_abort]$ ./test_random_abort -h ~/10789.HOME -v -T 5 mkdir: cannot create directory ‘..//home/sue/10789.HOME.SAVE’: No such file or directory Open database, run recovery and verify content ...
Definition of Done:
- The working directory can be specified using an absolute OR a relative path without errors.
EDIT: This issue affects random_abort, schema_abort and timestamp_abort.
- is related to
-
WT-14355 Incr_backup leaves nested test artefacts
-
- Closed
-
-
WT-14222 Write live restore file handle unit tests for fh_size and fh_truncate
-
- Closed
-
-
WT-14127 Switch over to V5 toolchain within all supported machines
-
- Closed
-
-
WT-14561 GCC 15 fixes
-
- Closed
-
-
WT-13661 Remove dead consecutive_unsuccessful_attempts variable
-
- Closed
-
- related to
-
WT-14288 Csuite tests fail with paths appended with /
-
- Open
-
-
WT-14283 csuite tests delete given database when verifying
-
- Open
-
-
WT-14560 Update README in test/csuite directory
-
- Needs Scheduling
-