ERROR: 1433 tests were run, 1 passed unexpectedly, 34 failed (5 expected failures). 646 tests were skipped. ## -------------------------- ## ## testsuite.log was created. ## ## -------------------------- ##
Please send `tests/testsuite.log' and all information you think might help: To: <b...@openvswitch.org> Subject: [openvswitch 2.5.90] testsuite: 15 407 938 939 940 941 1019 1020 1021 1033 1047 1050 1104 1767 1768 1769 1770 1771 1772 1773 1774 1775 1776 177 7 1778 1779 1780 2058 2070 failed, 1049 passed unexpectedly You may investigate any problem if you feel able to do so, in which case the test suite provides a good starting point. Its output may be found below `tests/testsuite.dir'. As a first run. Analyzing things in more detail. > -----Mesaj original----- > De la: Alin Serdean > Trimis: Wednesday, June 22, 2016 1:58 AM > Către: 'Lance Richardson' <lrich...@redhat.com> > Cc: dev@openvswitch.org > Subiect: RE: tests: fix issue in use of OVS_APP_EXIT_AND_WAIT > > Hi Lance, > > I applied your patch and testing it out right now. I'll let you know the > result as > soon as possible. > > > Initially I tried using 2015, but ran into multiple compilation issues > > (the first due to a type collision in pthread.h, easily fixed, I don't > > recall what I ran into next), then 2013, which compiled and built with > > no issues. However, when I tried to run the tests I saw a series of > > "entry point not found" pop-ups. Turns out OVS uses > > GetSystemTimePreciseAsFileTime(), which isn't supported on > [Alin Gabriel Serdean: ] OVS on Windows is targeted from Server 2012 > forwards (its Windows equivalent would be 8, you could also use 8.1 or 10). > Also for the moment we are compiling just with Visual Studio 2013 (update 4) > as per > https://github.com/openvswitch/ovs/blob/master/INSTALL.Windows.md > we will look into 2015 to see why is it failing as soon as we can. > > Windows 7 (it's only available on Windows 8 and 10). Updating to > > Windows 10 on the laptop I was using isn't an option (as I found out > > the hard way) because the manufacturer hasn't released display drivers for > Windows 10. > > > > Anyway, thanks for asking but I'm unlikely to pursue it any further > > (mainly due to a lack of time and lack of the right equipment). > > > > Regards, > > > > Lance > > _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
