+1 I built and run C++ test on Mac OS X 10.11.6, some of the test failed, but I don't think it's a blocker for the release, especially given the fact that macOS is a development-only platform.
98% tests passed, 6 tests failed out of 361 23 - hybrid_clock-test (Failed) 175 - sentry_authz_provider-test (Failed) 197 - sentry_client-test (Failed) 250 - ksck_remote-test (Timeout) 261 - kudu-tool-test.2 (Failed) 355 - trace-test (Failed) On Mon, Feb 25, 2019 at 2:19 PM Attila Bukor <[email protected]> wrote: > Just a small correction, the MacOS tests didn't fail due to lsof, I just > got confused. I had failures on CentOS due to lsof not being installed > which were fixed after it was. On MacOS I had the below failures, > neither connected to lsof: > > --- > 96% tests passed, 14 tests failed out of 361 > > Label Time Summary: > no_dist_test = 13.13 sec*proc (1 test) > no_tsan = 5.61 sec*proc (3 tests) > > Total Test time (real) = 8620.63 sec > > The following tests FAILED: > 127 - master_sentry-itest (Failed) > 134 - raft_consensus_nonvoter-itest (Failed) > 156 - tablet_copy_client_session-itest (Failed) > 175 - sentry_authz_provider-test (Failed) > 197 - sentry_client-test (Failed) > 261 - kudu-tool-test.2 (Failed) > 267 - rebalancer_tool-test.0 (Failed) > 268 - rebalancer_tool-test.1 (Failed) > 269 - rebalancer_tool-test.2 (Failed) > 270 - rebalancer_tool-test.3 (Failed) > 271 - rebalancer_tool-test.4 (Failed) > 280 - tablet_server-test (Failed) > 327 - net_util-test (Failed) > 355 - trace-test (Failed) > Errors while running CTest > --- > > This doesn't change my vote of course. > > Attila > > On Mon, Feb 25, 2019 at 07:49:17PM +0100, Attila Bukor wrote: > > +1 > > > > I ran all C++ tests with KUDU_ALLOW_SLOW_TESTS=1 both in DEBUG and > > RELEASE on CentOS 7.6. master_hms-itest failed in both build types for > > me, but as HMS integration is still not finished, I think that's fine - > > plus it might be an environmental issue if it didn't fail for others. > > > > I also ran the tests for the Java kudu-client where two stress tests > > failed: > > > > ITClientStress. testManyShortClientsGeneratingScanTokens > > ITClientStress. testMultipleSessions > > > > I believe this should be fine too. > > > > The build succeeded on MacOS, but a bunch of tests failed complaining > > about lsof - as MacOS is not officially supported, this also shouldn't > > be a problem. > > > > Docker build failed from the extracted build directory due to not being > > in a Git working directory and git rev-parse failing. I'll fix this > > later, but of course this is also not a blocker as Docker is still > > experimental and last time I checked it worked fine from the Git working > > directory. > > > > Long story short, I've ran into some failures, but none of them should > > be blockers. > > > > If the comments on the release notes draft are addressed, I'm happy with > > releasing this RC. > > > > Attila > > > > On Thu, Feb 21, 2019 at 10:00:23PM -0800, Adar Lieber-Dembo wrote: > > > +1 > > > > > > I ran all C++ tests with KUDU_ALLOW_SLOW_TESTS=1 in DEBUG mode on > > > Ubuntu 18.04 and CentOS 6.6. All passed except for a known Ubuntu 18 > > > failure (a variant of KUDU-2641). > > > > > > On Thu, Feb 21, 2019 at 5:54 PM helifu <[email protected]> > wrote: > > > > > > > > +1 > > > > * All C++ tests passed in debug/release/tsan mode on Debian8.9, > except asan; > > > > However, I think it's acceptable because the asan mode never > worked for me; > > > > * All Java tests passed on Debian8.9 using gradlew; > > > > > > > > > > > > 何李夫 > > > > 2019-02-22 09:54:53 > > > > > > > > -----邮件原件----- > > > > 发件人: [email protected] > <[email protected]> 代表 Andrew Wong > > > > 发送时间: 2019年2月21日 8:42 > > > > 收件人: dev <[email protected]> > > > > 主题: [VOTE] Apache Kudu 1.9.0-RC1 > > > > > > > > Hello Kudu devs! > > > > > > > > The Apache Kudu team is happy to announce the first release > candidate for Apache Kudu 1.9.0. > > > > > > > > Apache Kudu 1.9.0 is a minor release that offers many improvements > and fixes since the prior release. > > > > > > > > This is a source-only release. The artifacts have been staged here: > > > > https://dist.apache.org/repos/dist/dev/kudu/1.9.0-RC1/ > > > > > > > > Java convenience binaries in the form of a Maven repository are > staged here: > > > > > https://repository.apache.org/content/repositories/orgapachekudu-1028/ > > > > > > > > It is tagged in Git as 1.9.0-RC1 and the corresponding hash is the > > > > following: > > > > > https://gitbox.apache.org/repos/asf?p=kudu.git;a=commit;h=76e8af74e151c018de7e3d6aa34fadd49bf41601 > > > > < > https://git-wip-us.apache.org/repos/asf?p=kudu.git;a=commit;h=76e8af74e151c018de7e3d6aa34fadd49bf41601 > > > > > > > > > > A draft of the release notes can be found here: > > > > https://gerrit.cloudera.org/c/12389/ > > > > > > > > The KEYS file to verify the artifact signatures can be found here: > > > > https://dist.apache.org/repos/dist/release/kudu/KEYS > > > > > > > > I'd suggest going through the README and the release notes, building > Kudu, and running the unit tests. Testing out the Maven repo would also be > appreciated. > > > > > > > > The vote will run until Monday, February 25th at 11:59AM PST. This > is a bit over the suggested 72 hours due to the weekend. > > > > > > > > > > > > Thank you, > > > > Andrew > > > > >
