On Tue, Feb 16, 2016 at 10:46 AM, Jean-Daniel Cryans <[email protected]> wrote:
> On Tue, Feb 16, 2016 at 10:37 AM, Stack <[email protected]> wrote: > > > On Tue, Feb 16, 2016 at 9:25 AM, Jean-Daniel Cryans <[email protected] > > > > wrote: > > .. > > The link to the troubleshooting hole punching doc, from here > > > > > https://github.com/cloudera/kudu/blob/master/docs/installation.adoc#rhel_from_source > > , > > is broke FYI: > > > > > https://github.com/cloudera/kudu/blob/master/docs/troubleshooting.html#req_hole_punching > > > That's just because github is trying to render the adocs, when we generate > the site the html files will be there. We haven't generated a new site yet > for 0.7.0 and those instructions are new. > > Thanks. > > Wrong c++ version? > > > > You also need to use the enable toolset stuff when running cmake (like it > shows in the docs), else you get exactly those lines. Not sure about the > asciidoctor stuff. > > > Thanks. Cleaning out cmake cache and generated files -- w/ your help (smile) -- did the job. I was able to build kudu. Unit tests failed for me. That expected/known? 135/178 Test #147: sys_catalog-test .................. Passed 0.71 sec 136/178 Test #153: alter_table-randomized-test .......***Failed 1.20 sec Start 154: registration-test Start 157: master_replication-itest 137/178 Test #155: client_failover-itest .............***Failed 1.31 sec .... and a few others. Label Time Summary: no_dist_test = 10.32 sec no_tsan = 6.63 sec Total Test time (real) = 155.06 sec The following tests FAILED: 153 - alter_table-randomized-test (Failed) 155 - client_failover-itest (Failed) 156 - client-stress-test (Failed) 158 - master_failover-itest (Failed) 159 - raft_consensus-itest (Failed) 161 - ts_recovery-itest (Failed) 163 - delete_table-test (Failed) 164 - external_mini_cluster-test (Failed) 165 - linked_list-test (Failed) 166 - all_types-itest (Failed) 167 - remote_bootstrap-itest (Failed) 168 - tablet_replacement-itest (Failed) 169 - create-table-itest (Failed) 172 - flex_partitioning-itest (Failed) 176 - kudu-admin-test (Failed) 177 - kudu-ts-cli-test (Failed) > > > > > > > > [stack@ve0524 debug]$ sudo yum install libatomic > > > > Loaded plugins: fastestmirror, priorities, security > > > > Setting up Install Process > > > > Loading mirror speeds from cached hostfile > > > > 124 packages excluded due to repository priority protections > > > > Package libatomic-4.9.0-6.1.1.el6.x86_64 already installed and latest > > > > version > > > > Nothing to do > > > > > > > > > > > > Tried to build docs and got this: > > > > > > > > [stack@ve0524 apache-kudu-incubating-0.7.0]$ pwd > > > > /home/stack/apache-kudu-incubating-0.7.0 > > > > [stack@ve0524 apache-kudu-incubating-0.7.0]$ make docs > > > > make: Nothing to be done for `docs'. > > > > > > > > > > Pretty sure that's because cmake above failed. > > > > > > > > Maybe the above complaint install asciidoc? > > > > Nah a missing target is just cmake failing to generate the files make > needs. > > make docs worked after kudu built. They look great (You don't want to put a version on them?) > > > "Also by default, building the CSD does not validate it, > > > because (for the moment) this requires access to an internal > > > Cloudera repository containing the validator maven plugin." > > > > > > Is above still the case? > > > > > > > Yes. Do you think the CSD should live somewhere else? > > > > > Smile. I don't know what a CSD is (though I'm guessing I should). It goes > undefined. > > When you say 'for the moment' in the above, it implies you are working on > moving this tooling out of Cloudera to a public place. As long as that is > ongoing, that seems fine to me. > I don't think there's a plan for this. Lemme check. I know what a CSD is now (thanks JD) but yeah, a sentence or two would alleviate new folks wondering if this important or not. St.Ack > > Thanks, > St.Ack > > > > > > > > > > > > > St.Ack > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Feb 11, 2016 at 6:55 PM, Jean-Daniel Cryans < > [email protected] > > > > > > wrote: > > > > > > > Hi, > > > > > > > > Here's the second release candidate for Apache Kudu (incubating) > 0.7.0. > > > > > > > > The is a source-only release. The artifacts were staged here: > > > > https://dist.apache.org/repos/dist/dev/incubator/kudu/0.7.0-RC2/ > > > > > > > > It was built from this tag: > > > > > > > > > > > > > > https://git1-us-west.apache.org/repos/asf?p=incubator-kudu.git;a=commit;h=899d79a246161b4429663f23d135bc8fdcac4372 > > > > > > > > The list of all issues fixed is found following this link > > > > < > > > > > > > > > > https://issues.cloudera.org/issues/?jql=project%20%3D%20Kudu%20AND%20status%20in%20%20(Resolved)%20AND%20fixVersion%20%3D%200.7.0%20ORDER%20BY%20key%20ASC > > > > > > > > > . > > > > > > > > The following commits made it in since the last RC: > > > > 899d79a Set -rpath in all thirdparty libs for compat with gold > > > > a9af916 Reorg of release notes to be more flexible as we add more > > > releases > > > > in future > > > > b3eb88e Update NOTICE.txt to include Apache copyright > > > > > > > > The release notes are found here (linking to github for prettier > > > printing): > > > > > > > > > > > > > > https://github.com/cloudera/kudu/blob/0.7.0-RC2/docs/release_notes.adoc#release-notes-specific-to-0-7-0 > > > > > > > > KEYS file: > > > > http://www.apache.org/dist/incubator/kudu/KEYS > > > > > > > > I'd suggest going through the README, building Kudu, and running the > > unit > > > > tests. > > > > > > > > Please try the release and vote; vote will be open for at least 120 > > hours > > > > (due to the long weekend in the US). > > > > > > > > Thanks, > > > > > > > > J-D > > > > > > > > > >
