-
Type: Improvement
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
3
-
Storage - Ra 2021-01-11
If anyone wants to run wt3120_filesys, they might try running it this way and get the below error:
$cd build_posix/test/csuite $ ./test_wt3120_filesys Running test command: ./test_wt3120_filesys [1609371223:503738][14791:0x7f0ed5ae7740], wiredtiger_open: __wt_dlopen, 25: dlopen(../../build_posix/ext/test/fail_fs/.libs/libwiredtiger_fail_fs.so): ../../build_posix/ext/test/fail_fs/.libs/libwiredtiger_fail_fs.so: cannot open shared object file: No such file or directory: WT_ERROR: non-specific WiredTiger error test_wt3120_filesys: FAILED: main/59: wiredtiger_open(opts->home, NULL, buf, &opts->conn): WT_ERROR: non-specific WiredTiger error test_wt3120_filesys: process aborting Aborted (core dumped)
Unfortunately, that results in an error (abort of a subprocess). It's not at all apparent that this test must be run as:
$ cd build_posix/test $ ./csuite/test_wt3120_filesys Running test command: ./csuite/test_wt3120_filesys Success
The directory position is relevant because a shared library extension is used for the test, and it is specified as a relative pathname. make check apparently runs the test from the build_posix/test directory, which is why it needs to continue to work from there.
- is duplicated by
-
WT-5111 Fix wt2909_checkpoint_integrity and wt3120_filesys so it is natural to run standalone
- Closed