github/open-cas-linux
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Do not run test_core_device_error in lazy write cache modes

Browse Source 
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>
This commit is contained in:
Rutkowski, Adam J 2022-09-26 11:10:06 +02:00
parent d6eebc2cc3
commit 349ec69f65
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
test/functional/tests/fault_injection/test_primary_device_error.py
View File

@ -12,6 +12,7 @@ from core.test_run import TestRun
from api.cas import casadm
from api.cas.cache_config import (
CacheMode,
CacheModeTrait,
CacheLineSize,
SeqCutOffPolicy,
CleaningPolicy,
@ -22,7 +23,7 @@ from test_utils.size import Size, Unit
@pytest.mark.parametrizex("cache_line_size", CacheLineSize)
@pytest.mark.parametrizex("cache_mode", CacheMode)
@pytest.mark.parametrizex("cache_mode", CacheMode.without_traits(CacheModeTrait.LazyWrites))
@pytest.mark.parametrizex("io_dir", [ReadWrite.randread, ReadWrite.randwrite])
@pytest.mark.require_disk("cache", DiskTypeSet([DiskType.optane, DiskType.nand]))
@pytest.mark.require_disk("core", DiskTypeLowerThan("cache"))