diff options
| author |   Martin Klozik <martinx.klozik@intel.com> | 2016-01-11 12:58:28 +0000 |
|---|---|---|
| committer |   Maryam Tahhan <maryam.tahhan@intel.com> | 2016-01-11 13:23:40 +0000 |
| commit | f9151087699b72fea457b6c8ea6d3b1c69d70c36 (patch) | |
| tree | 37c49898e41c841d86abdc5563c9aefae0e768a1 /core/component_factory.py | |
| parent | 8dd24de9da39c1f863d5cf0e5a24e744fa0459d3 (diff) | |
CI: terminate hanging vsperf before its execution
In case that vsperf terminates unexpectedly, then vsperf itself
or any of executed applications might remain active. It is essential
to terminate any hanging instance of vsperf, ovs, qemu, etc.
before re-execution of vsperf itself. Otherwise vsperf will fail
again.
Change-Id: Idd65288a5171d19fcbfb907a156347eb4b645a88
JIRA: VSPERF-155
Signed-off-by: Martin Klozik <martinx.klozik@intel.com>
Reviewed-by: Maryam Tahhan <maryam.tahhan@intel.com>
Reviewed-by: Al Morton <acmorton@att.com>
Reviewed-by: Brian Castelli <brian.castelli@spirent.com>
Reviewed-by: Gurpreet Singh <gurpreet.singh@spirent.com>
Reviewed-by: Tv Rao <tv.rao@freescale.com>
(cherry picked from commit b2b11bf301bbe37befdda23e2a0f1501c079405f)
Diffstat (limited to 'core/component_factory.py')
0 files changed, 0 insertions, 0 deletions