New test kernel_multipath_flakyserver #8539
Conversation
|
What am I supposed to do about the Travis CI build fail? The reported details (an early perl version problem) don't look related to this PR. |
This is the perl version that's being used in production: => https://travis-ci.org/os-autoinst/os-autoinst-distri-opensuse/jobs/589432066#L414 Here's another failure in static checks: https://travis-ci.org/os-autoinst/os-autoinst-distri-opensuse/jobs/589432067#L570 (https://travis-ci.org/os-autoinst/os-autoinst-distri-opensuse/jobs/589432068#L453) you should be able to run: in your local box, to be able to reproduce most of the failures. |
klwagner
force-pushed
the
190731-multipathtest_flakyserver
branch
2 times, most recently
from
e74cff9
to
b87e6bb
Compare
klwagner
force-pushed
the
190731-multipathtest_flakyserver
branch
from
b87e6bb
to
301cf8b
Compare
|
New verification runs:
|
klwagner
force-pushed
the
190731-multipathtest_flakyserver
branch
from
301cf8b
to
a5b3796
Compare
|
This commit manages to run both intended testcases rather than only one. |
klwagner
force-pushed
the
190731-multipathtest_flakyserver
branch
from
a5b3796
to
28cecf7
Compare
klwagner
force-pushed
the
190731-multipathtest_flakyserver
branch
3 times, most recently
from
5d760d9
to
69429ab
Compare
|
5d760d9 is to ignore. Difference of 69429ab vs. 28cecf7: Apart from some cosmetics (comments etc.) module New verification runs: client 563 server 562 |
Incorporate new test into existing client module qa_kernel_multipath.pm and add associated new supportserver module flaky_mp_iscsi.pm. If variable 'ISCSI_MULTIPATH_FLAKY' is set, qa_kernel_multipath.pm, rather than running the standard "qa_sw_multipath" testsuite, will run just variants of its two I/O-intensive testcases. The difference is that it is the server rather than the client itself which will proceed to (randomly) disturb the paths of the multipathed block device under test while the client is just doing heavy I/O. Expected result is that the client is able to cope without any errors (I/O or others). Many extra comments and some debug statements and FIXMEs are left in. FIXME: as commented in-code, subs qaset_waitdone() and qaset_waitstop() in kernel_multipath.pm are not really satisfactory. Reference: qaset API request https://progress.opensuse.org/issues/58253
klwagner
force-pushed
the
190731-multipathtest_flakyserver
branch
from
69429ab
to
23a1d95
Compare
klwagner
changed the title
A modification of two testcases from the standard
qa_sw_multipathtestsuite.After importing one multipathed disk via iSCSI from the support server
the client runs modifications of the
active_activeandactive_passivetests.The difference is that it is the server rather than the client which will proceed to
(randomly) disable multipaths while the client is just doing heavy I/O.
Expected result is that the client is able to cope without any errors
(I/O or others).
Many extra comments and some debug statements and FIXMEs are left in.