Files
scst/tests/ginkgo/config.example.json
Gleb Chesnokov 3d069d3ee0 tests: Cover fileio sync across backend detach and reactivation
The sysfs sync regression in issue #394 originates in
commit 530af782ed ("scst_vdisk: Add 'sync' sysfs attribute").
It dereferenced a closed file. Require a management rejection for inactive
devices, the last detach and ALUA states that close the backend, then
verify recovery.

Remove only the fixture device's internal copy-manager mappings when
checking the last attachment: an external LUN count alone does not prove
that the backend is closed. Use an explicit local session for successful
sync and preserve unrelated devices. Put session LUNs in an explicit
initiator group because scstadmin does not report the default group map
in its session listing.

Drop the temporary known-crash label, opt-in setting and example filter.
The inactive-sync regression now belongs to the default basic selection.

Link: https://github.com/SCST-project/scst/issues/394
2026-10-14 17:39:14 +03:00

24 lines
526 B
JSON

{
"admin_command": ["scstadmin"],
"disposable_host": false,
"name_prefix": "scsttest",
"report_dir": "results",
"lock_file": "/tmp/scst-ginkgo.lock",
"command_timeout": "30s",
"cleanup_timeout": "2m",
"settle_timeout": "10s",
"poll_interval": "100ms",
"suite_timeout": "15m",
"build_timeout": "10m",
"build_jobs": 2,
"backing_dir": "",
"fileio_thin_provisioning": true,
"stress_iterations": 8,
"scale_luns": 256,
"io": {
"block_device": "",
"region_mb": 64,
"timeout": "3m"
}
}