Testing on a single CPU machine is problematic (even if it would have run fast), but the build itself has its own advantage. The driver build should be much quicker.
Do we use precompiled header option? https://msdn.microsoft.com/en-us/library/2yzw0wyd.aspx Thanks, Eitan -----Original Message----- From: dev [mailto:dev-boun...@openvswitch.org] On Behalf Of Gurucharan Shetty Sent: Thursday, February 05, 2015 1:27 PM To: Ben Pfaff Cc: dev; Gurucharan Shetty Subject: Re: [ovs-dev] [PATCH 2/2] appveyor: Provide a autobuild service for Windows. > > Oh! > > Do you have an idea of what takes up the bulk of the time for the OVS > unit tests in Windows? I think the main reasons are: * Creation of new processes is slow on Windows. So some unit tests that run hundreds of processes causes the unit tests to go very slow (for e.g., bfd and cfm). * I think 'configure' is also slow on Windows for the same reason as above. * autoconf tests on mingw does not have the infrastructure to be executed in parallel. (I think it is because of no mknod. Probably it can be worked around, but the fix will likely be needed upstream in the code that generates testsuite) * Appveyor itself provides only one CPU. So I cannot run 'make -jx' _______________________________________________ dev mailing list dev@openvswitch.org https://urldefense.proofpoint.com/v2/url?u=http-3A__openvswitch.org_mailman_listinfo_dev&d=AwIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=CWsgHUxi6ExLXY798tmo3LJ4e3geGYp56lkcH-5cLCY&m=GX0hr7CUW9JW_B5yLYnNDaWDoO-5-MOBGFO8vOZDujU&s=Cw_TEP7eHYIGXE0sNkC55mer7x-Wa10Uxrm9m0XrVC0&e= _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
