+1 - Built in TSAN mode on Ubuntu 16.04 - Ran tests. Most passed except master-test (filed KUDU-2361). Then my computer crashed, taking down the 1.7 build output (which was in /tmp) with it.
On Tue, Mar 20, 2018 at 10:09 AM, William Berkeley <[email protected]> wrote: > +1 > > - Built in debug mode on macOS and el7. > - Ran tests, all passed except the macOS issues Alexey has addressed. I > don't think the macOS test-only issues are a big deal. > - Did some basic insert/update/scan operations on a loadgen table. > > -Will > > On Tue, Mar 20, 2018 at 9:24 AM, Alexey Serbin <[email protected]> wrote: > >> Yep, it seems the failure of those 3 tests should not be a show-stopper for >> the 1.7 release since macOS is a development-only platform: >> >> delete_table-itest >> master-test >> rpc-test >> >> >> Thanks, >> >> Alexey >> >> >> >> On 3/20/18 8:52 AM, Grant Henke wrote: >> >>> Thanks for the correction Alexey. >>> >>> For anyone reading.* Today (March 20th) is the intended last day of the >>> vote*. Given I listed Tuesday, I hope that date error wasn't too >>> confusing. >>> >>> I am not sure an Mac OSX test issue is enough that it warrant's a new RC. >>> Given it only affects development on an experimental system. We can cherry >>> pick them to 1.7.x to ensure they don't impact future >>> development/cherry-pick work in the branch. Does that seam reasonable? >>> >>> Thank you, >>> Grant >>> >>> On Tue, Mar 20, 2018 at 1:01 AM, Todd Lipcon <[email protected]> wrote: >>> >>> +1 >>>> >>>> - Downloaded and verified signature and sha1. My signature is attached >>>> below >>>> - built on el7 DEBUG using gcc 4.8.5. ran tests. >>>> - built on el7 using devvtoolset-7 (gcc 7). ran tests. >>>> - got a few failures in both configs, but they passed upon re-running. I >>>> was running them in parallel with each other on the same temp disk so I >>>> think it was just various timeouts due to the disk being overloaded. >>>> - did various failure testing of the new "3-4-3" replication scheme on a >>>> 6-node cluster >>>> - did basic validation on a 125-node cluster running Kudu with Impala >>>> including some 100B-row inserts (which discovered some bugs earlier in >>>> the >>>> 1.7 release cycle and now seem OK). A few nodes went down during the >>>> testing and everything seems to have recovered fine. >>>> >>>> >>>> >>>> >>>> -----BEGIN PGP SIGNATURE----- >>>> Version: GnuPG v1 >>>> >>>> iEYEABECAAYFAlqweKUACgkQXkPKua7Hfq+7DQCg4t6llqevULFCmEIzGHrh7YSv >>>> nXoAoPvJUrYpP46KC1TQP/exD57qS3TO >>>> =+kkn >>>> -----END PGP SIGNATURE----- >>>> >>>> >>>> >>>> On Fri, Mar 16, 2018 at 6:28 PM, Grant Henke <[email protected]> >>>> wrote: >>>> >>>> Hi, >>>>> >>>>> The Apache Kudu team is happy to announce the second release candidate >>>>> >>>> for >>>> >>>>> Apache Kudu 1.7.0. >>>>> >>>>> Apache Kudu 1.7.0 is a minor release that offers many improvements and >>>>> fixes since the prior release. >>>>> >>>>> The is a source-only release. The artifacts have been staged here: >>>>> https://dist.apache.org/repos/dist/dev/kudu/1.7.0-RC2/ >>>>> >>>>> Java convenience binaries in the form of a Maven repository are staged >>>>> here: >>>>> https://repository.apache.org/content/repositories/orgapachekudu-1019/ >>>>> >>>>> It is tagged in Git as 1.7.0-RC2 and the corresponding git hash is the >>>>> following: >>>>> https://git-wip-us.apache.org/repos/asf?p=kudu.git;a=commit; >>>>> h=472ae66565d9a8efdc81f16568249d7c4b108251 >>>>> >>>>> The release notes can be found here: >>>>> https://github.com/apache/kudu/blob/1.7.0-RC2/docs/release_notes.adoc >>>>> >>>>> 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 Tuesday, March 6th at 11PM PDT. We'd normally >>>>> run a vote for 3 full days but since we're headed into the weekend now >>>>> let's do 4 days instead. >>>>> >>>>> Thank you, >>>>> Grant >>>>> >>>>> >>>>> -- >>>>> Grant Henke >>>>> Software Engineer | Cloudera >>>>> [email protected] | twitter.com/gchenke | linkedin.com/in/granthenke >>>>> >>>>> >>>> >>>> -- >>>> Todd Lipcon >>>> Software Engineer, Cloudera >>>> >>>> >>> >>> >>
