On Windows, we really do not have any "socket" files created. We instead create a regular file with a TCP port number written inside it.
Signed-off-by: Gurucharan Shetty <gshe...@nicira.com> --- tests/ovsdb-server.at | 18 +++++++++++++++--- 1 file changed, 15 insertions(+), 3 deletions(-) diff --git a/tests/ovsdb-server.at b/tests/ovsdb-server.at index 77b7dc1..155d418 100644 --- a/tests/ovsdb-server.at +++ b/tests/ovsdb-server.at @@ -384,14 +384,22 @@ AT_CHECK([ovsdb-server --detach --no-chdir --pidfile db]) AT_CHECK([test ! -e socket1]) AT_CHECK([ovs-appctl -t ovsdb-server ovsdb-server/add-remote punix:socket1]) -OVS_WAIT_UNTIL([test -S socket1]) +if test "$IS_WIN32" = "yes"; then + OVS_WAIT_UNTIL([test -s socket1]) +else + OVS_WAIT_UNTIL([test -S socket1]) +fi AT_CHECK([ovs-appctl -t ovsdb-server ovsdb-server/list-remotes], [0], [punix:socket1 ]) AT_CHECK([test ! -e socket2]) AT_CHECK([ovs-appctl -t ovsdb-server ovsdb-server/add-remote punix:socket2]) -OVS_WAIT_UNTIL([test -S socket2]) +if test "$IS_WIN32" = "yes"; then + OVS_WAIT_UNTIL([test -s socket2]) +else + OVS_WAIT_UNTIL([test -S socket2]) +fi AT_CHECK([ovs-appctl -t ovsdb-server ovsdb-server/list-remotes], [0], [punix:socket1 punix:socket2 @@ -404,7 +412,11 @@ ovs-appctl: ovsdb-server: server returned an error AT_CHECK([ovs-appctl -t ovsdb-server ovsdb-server/remove-remote punix:socket1]) OVS_WAIT_UNTIL([test ! -e socket1]) -AT_CHECK([test -S socket2]) +if test "$IS_WIN32" = "yes"; then + AT_CHECK([test -s socket2]) +else + AT_CHECK([test -S socket2]) +fi AT_CHECK([ovs-appctl -t ovsdb-server ovsdb-server/list-remotes], [0], [punix:socket2 ]) -- 1.7.9.5 _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
