tests: Fix issue in use of OVS_APP_EXIT_AND_WAIT.
authorLance Richardson <lrichard@redhat.com>
Fri, 10 Jun 2016 16:17:57 +0000 (12:17 -0400)
committerBen Pfaff <blp@ovn.org>
Thu, 23 Jun 2016 23:05:10 +0000 (16:05 -0700)
commit8a16ab90b27ca28fbc5e8a42a02eb8c7133183ae
tree8a4ed8f80a80f3281465ec13aacdc2d17b634283
parent42814145d70c77462ce28b38841cd160f0486776
tests: Fix issue in use of OVS_APP_EXIT_AND_WAIT.

Commit f9b11f2a09b4 introduced a loop to wait for process exit
in OVS_APP_EXIT_AND_WAIT after the "exit" command has been sent.
Unfortunately, this does not work for cases where a unixctl socket
has to be used to send the "exit" command because the process
ID cannot be determined from the socket path.

OVS_APP_EXIT_AND_WAIT_BY_TARGET has since been introduced to enable
graceful termination of daemons via unixctl sockets.

This set of changes addresses the problem described above by
making OVS_APP_EXIT_AND_WAIT_BY_TARGET take the unixctl socket
path and corresponding process ID as separate parameters. In order
to better detect issues in this logic in the future, checks have
been added to verify that the pidfile exists before using its
contents.

Tested on a Linux system.

Signed-off-by: Lance Richardson <lrichard@redhat.com>
Signed-off-by: Ben Pfaff <blp@ovn.org>
tests/daemon.at
tests/ovn-controller.at
tests/ovn-sbctl.at
tests/ovs-macros.at
tests/ovs-vsctl.at
tests/ovs-vswitchd.at
tests/ovsdb-idl.at
tests/ovsdb-monitor.at
tests/ovsdb-server.at