Re: [PATCH v2] iotests: Write test output to TEST_DIR

2022-02-22 Thread Vladimir Sementsov-Ogievskiy
22.02.2022 17:44, Hanna Reitz wrote: On 22.02.22 15:39, Vladimir Sementsov-Ogievskiy wrote: 21.02.2022 20:29, Hanna Reitz wrote: Drop the use of OUTPUT_DIR (test/qemu-iotests under the build directory), and instead write test output files (.out.bad, .notrun, and .casenotrun) to TEST_DIR. With

Re: [PATCH v2] iotests: Write test output to TEST_DIR

2022-02-22 Thread Hanna Reitz
On 22.02.22 15:39, Vladimir Sementsov-Ogievskiy wrote: 21.02.2022 20:29, Hanna Reitz wrote: Drop the use of OUTPUT_DIR (test/qemu-iotests under the build directory), and instead write test output files (.out.bad, .notrun, and .casenotrun) to TEST_DIR. With this, the same test can be run

Re: [PATCH v2] iotests: Write test output to TEST_DIR

2022-02-22 Thread Vladimir Sementsov-Ogievskiy
21.02.2022 20:29, Hanna Reitz wrote: Drop the use of OUTPUT_DIR (test/qemu-iotests under the build directory), and instead write test output files (.out.bad, .notrun, and .casenotrun) to TEST_DIR. With this, the same test can be run concurrently without the separate instances interfering,

[PATCH v2] iotests: Write test output to TEST_DIR

2022-02-21 Thread Hanna Reitz
Drop the use of OUTPUT_DIR (test/qemu-iotests under the build directory), and instead write test output files (.out.bad, .notrun, and .casenotrun) to TEST_DIR. With this, the same test can be run concurrently without the separate instances interfering, because they will need separate TEST_DIRs