Rutkowski, Adam J 349ec69f65 Do not run test_core_device_error in lazy write cache modes ... This test has multiple assumptions that do not hold for WB/WO: 1. it assumes primary storage errors would propagate to user I/O 2. cache is stopped with metadata flush, which would fail 3. after stopping CAS core content is verified with fio 4. cache is so small that it overfills, resulting in PT I/O further complicating error accounting. Signed-off-by: Rutkowski, Adam J <adam.j.rutkowski@intel.com>		2022-09-26 11:10:06 +02:00
..
functional	Do not run test_core_device_error in lazy write cache modes	2022-09-26 11:10:06 +02:00
smoke_test	Update smoke_tests	2022-03-28 12:43:57 +02:00
utils_tests/opencas-py-tests	Add missing license headers	2022-07-22 09:17:16 +02:00