I noticed that windows trunk build has been broken for some time. I updated to use the recent work by Andrew Schwartzmeyer. We are now able to use cmake to successfully build the c binding on the Windows Jenkins hosts. https://builds.apache.org/view/S-Z/view/ZooKeeper/job/ZooKeeper-trunk-windows-cmake/ notice that this is compiling the jute bindings on Windows and then building on Windows (30 warnings on the c code). We aren't actually running the tests.
Patrick On Mon, Oct 2, 2017 at 7:41 AM, Patrick Hunt <[email protected]> wrote: > Hi folks. I've been working on cleaning up the Jenkins jobs > https://builds.apache.org/view/S-Z/view/ZooKeeper/ > we were having a number of failures. In particular there were some issues > with the build.xml and conflicting library versions being pulled in. Also > some changes to INFRA backend had caused some of the Jenkins jobs to always > fail (esp openjdk). I've cleaned this all up (along with some help from > Abe) and we're seeing a more stability. > > Note: Apache INFRA updated jenkins and all of the plugins over the weekend > so we'll have to see if there's any fallout from that. > > Additionally I've also added java9 jobs for branches 3.4 and 3.5. So far > the main issue looks like a single test is failing continually. > https://issues.apache.org/jira/browse/ZOOKEEPER-2908 > > As part of the Jenkins changes I also updated the flakey test reporting > dashboard > https://builds.apache.org/view/S-Z/view/ZooKeeper/job/ > ZooKeeper-Find-Flaky-Tests/lastSuccessfulBuild/artifact/report.html > Some good areas to work on there if folks are looking. Notice that Abe has > posted a few patches to GH already that should be looked through: > https://github.com/apache/zookeeper/pulls?utf8=%E2%9C% > 93&q=is%3Apr%20is%3Aopen%20flaky > > Regards, > > Patrick >
