[ovs-discuss] Windows Unit Failed Tests summary
aserdean at ovn.org
aserdean at ovn.org
Tue Jul 31 13:01:11 UTC 2018
Hi,
The following unit tests fail under Windows:
mpls-xlate
454: MPLS xlate action FAILED
(mpls-xlate.at:132)
tunnel
805: tunnel - ERSPAN v1/v2 metadata FAILED (tunnel.at:586)
ofproto
966: ofproto - flow table names FAILED
(ofproto.at:2716)
OVSDB -- interface description language (IDL)
2071: simple idl, writing large data via IDL with unicode - Python3 FAILED
(ovsdb-idl.at:400)
ovn-nbctl
2607: ovn-nbctl - commands parser error paths FAILED
(ovn-nbctl.at:1535)
I am debugging 454, 805, 966 and will try to see what we are missing.
I want to disable the test 2071 because of the MBCS shell pitfalls.
Other tests that use Unicode pass but there is a problem when
parsing large arguments.
I need some guidance on 2607. A bit more background we are
using the BSD variant of getopt, and there are some slight
differences.
I tried updating:
https://github.com/openvswitch/ovs/blob/master/lib/getopt_long.c
to the latest BSD variant but it still is not 100% compatible with the
GNU one.
Does anyone have some opinions if I should change the
test and/or code?
I'm including also the logged output:
# -*- compilation -*-
2607. ovn-nbctl.at:1503: testing ovn-nbctl - commands parser error paths ...
./ovn-nbctl.at:1504: ovsdb-tool create ovn-nb.db
$abs_top_srcdir/ovn/ovn-nb.ovsschema
./ovn-nbctl.at:1504: ovsdb-server --detach --no-chdir --pidfile --log-file
--remote=punix:$OVS_RUNDIR/ovnnb_db.sock ovn-nb.db
stderr:
./ovn-nbctl.at:1504: ovn-nbctl init
./ovn-nbctl.at:1504: sed < stderr '
/vlog|INFO|opened log file/d
/ovsdb_server|INFO|ovsdb-server (Open vSwitch)/d'
./ovn-nbctl.at:1510: ovn-nbctl -- --if-exists --if-exists list
Logical_Switch
stderr:
ovn-nbctl: '--if-exists' option specified multiple times
./ovn-nbctl.at:1511: grep 'option specified multiple times' stderr
stdout:
ovn-nbctl: '--if-exists' option specified multiple times
./ovn-nbctl.at:1514: ovn-nbctl
stderr:
ovn-nbctl: missing command name (use --help for help)
./ovn-nbctl.at:1515: grep 'missing command name' stderr
stdout:
ovn-nbctl: missing command name (use --help for help)
./ovn-nbctl.at:1517: ovn-nbctl --if-exists
stderr:
ovn-nbctl: missing command name (use --help for help)
./ovn-nbctl.at:1518: grep 'missing command name' stderr
stdout:
ovn-nbctl: missing command name (use --help for help)
./ovn-nbctl.at:1520: ovn-nbctl --
stderr:
ovn-nbctl: missing command name (use --help for help)
./ovn-nbctl.at:1521: grep 'missing command name' stderr
stdout:
ovn-nbctl: missing command name (use --help for help)
./ovn-nbctl.at:1523: ovn-nbctl -- --if-exists
stderr:
ovn-nbctl: missing command name (use --help for help)
./ovn-nbctl.at:1524: grep 'missing command name' stderr
stdout:
ovn-nbctl: missing command name (use --help for help)
./ovn-nbctl.at:1527: ovn-nbctl foo
stderr:
ovn-nbctl: unknown command 'foo'; use --help for help
./ovn-nbctl.at:1528: grep 'unknown command' stderr
stdout:
ovn-nbctl: unknown command 'foo'; use --help for help
./ovn-nbctl.at:1530: ovn-nbctl -- foo
stderr:
ovn-nbctl: unknown command 'foo'; use --help for help
./ovn-nbctl.at:1531: grep 'unknown command' stderr
stdout:
ovn-nbctl: unknown command 'foo'; use --help for help
./ovn-nbctl.at:1534: ovn-nbctl --foo list Logical_Switch
stderr:
2018-07-31T12:23:53Z|00001|getopt_long|WARN|unknown option -- foo
./ovn-nbctl.at:1535: grep 'unrecognized option' stderr
stdout:
./ovn-nbctl.at:1535: exit code was 1, expected 0
Thanks,
Alin.
More information about the discuss
mailing list