Hi Ilya, Thanks for your feedback!
> Hi, Sergey and William. Thanks for working on this. > > I think that it might be a good idea to move to a different build system > that will not be that painful to run on Windows. I'm not working on > Windows parts, but it would be great to have a fast CI that can confirm > that everything still working fine. Yes, and avoiding the msys/mingw makes coding and debugging on windows much easier. > > However, as I already said in the discussion on GitHub, it seems to be > very hard to migrate our testsuite that heavily depends on autotest. > And without migrating the testsuite we will, probably, have to maintain > two different build systems to be able to run tests. This, kind of, > defeats the whole purpose of the change. Why is it very hard? I thought once we find a way to add tests to meson, it's just "mechanically" copying all these scripts into a new test framework. It's a lot of tedious work, but hopefully not a difficult or impossible task. Or does current OVS autotests heavily depend on autotool/autoconf? I see the test cases are pretty independent. > > Meson is a nice system in many aspects, but its support for tests is very > limited. IIUC, it can only run a single binary and check the error codes. > Most of our tests starts several daemons and performs several fairly complex > operations and checks. I'm afraid that we will end up writing our own > separate testing framework that will mimic autotest in order to be able to > run our tests from meson. > > Did you think about this problem? Do you have a solution in mind? Thanks, we thought about it but I don't have a solution in mind at this moment. Regards, William _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
