c8a36b04cb
We currently use a hack AllowDuplicatedIsid with the iSCSI target to allow running multiple Calsoft tests in parallel, since each Calsoft test always uses the same InitiatorName. But this causes some tests to intermittently fail, likely due to changed behavior with many sessions sharing the same InitiatorName. The problem is very difficult to reproduce, and made worse since the Calsoft tests themselves are binary only. So instead split the tests into two sets - one set contains nopin-related tests which each take longer to run due to various interval expirations needed for the test. There are just a few of these tests, and do not appear to ever cause an intermittent failure, so we run these in parallel. The rest are all run serially and run rather quickly. Fixes issue #2416. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: I0bd29da8a71d4c7593bba11f1e2f2e11e2289d8a Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/16022 Reviewed-by: Michal Berger <michal.berger@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Shuhei Matsumoto <smatsumoto@nvidia.com> Reviewed-by: Kamil Godzwon <kamilx.godzwon@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> |
||
|---|---|---|
| .. | ||
| calsoft.py | ||
| calsoft.sh | ||
| iscsi.json | ||
| its.conf | ||