5854d3c0a5
This test suite was doing some things as far as formatting that are covered by the run_test framework. Also, the way the tet cases were organized was obfuscating which migration tests are actually being run in the autotest jobs. This configuration makes it a lot easier to manage. As a side note, migration-tc3a.sh and migration-tc3b are not referenced anywhere in the test scripts. They may be extraneous. Change-Id: Ibe6782b38cb87c90b2bc61f112f10cd35f5b4a44 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/476937 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Community-CI: SPDK CI Jenkins <sys_sgci@intel.com> |
||
|---|---|---|
| .. | ||
| autotest.config | ||
| migration-tc1.job | ||
| migration-tc1.sh | ||
| migration-tc2.job | ||
| migration-tc2.sh | ||
| migration-tc3.job | ||
| migration-tc3a.sh | ||
| migration-tc3b.sh | ||
| migration.sh | ||