Thanks Todd. My primary concern was actually that we got repository.a.o setup properly. (staging) Re that issue you'I worked on a few months ago - the zookeeper test jar was missing. I assume that if any of the ZK tests are passing then that aspect is functioning properly? I eyeballed the repo and it looked correct (the test jar is there) but I wanted to verify by running Hadoop tests themselves.
btw. the module kept running all the tests, but then stopped after all the tests within that module were run. It didn't continue with addl modules. But it did run all the tests w/in the failing module. I tried setting failOnError (whatever it is) in mvn to false, but that didn't help, which is odd.... Thanks! Patrick On Fri, Mar 7, 2014 at 6:30 PM, Todd Lipcon <[email protected]> wrote: > On Fri, Mar 7, 2014 at 2:44 PM, Patrick Hunt <[email protected]> wrote: >> >> I still can't get through all the Hadoop tests in 2.3.0, I even tried >> another machine. It does get further on another machine, but there >> seem to be flakey tests (not zk related) that always keep the full >> suite from completing. > > > It ought to keep running even if some of the tests failed. Surprising that > it doesn't. Maybe run each module's tests sepately rather than mvn test from > toplevel? > >> >> >> I did notice that the zookeeper jar and test jar is pulled down >> successfully from the staging environment (when I update hadoop to use >> 3.4.6 staging). >> >> The following tests reference zk, and they pass, so at this point I'm >> going to give up and assume that we're good. :-) I'm ccing Todd, >> perhaps he can give us some insight into whether this set of tests >> covers most of what hadoop tests re zk use: >> >> Running org.apache.hadoop.ha.TestActiveStandbyElectorRealZK >> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 11.185 >> sec - in org.apache.hadoop.ha.TestActiveStandbyElectorRealZK >> Running org.apache.hadoop.ha.TestZKFailoverController >> Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: >> 45.351 sec - in org.apache.hadoop.ha.TestZKFailoverController >> Running org.apache.hadoop.ha.TestZKFailoverControllerStress >> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 94.119 >> sec - in org.apache.hadoop.ha.TestZKFailoverControllerStress >> Running org.apache.hadoop.util.TestZKUtil >> Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.132 >> sec - in org.apache.hadoop.util.TestZKUtil >> Running >> org.apache.hadoop.hdfs.server.namenode.ha.TestDFSZKFailoverController >> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 23.09 >> sec - in >> org.apache.hadoop.hdfs.server.namenode.ha.TestDFSZKFailoverController > > > Those look like a good set from the common side. MR has a few tests like > TestZKRMStateStore which might be useful, but I don't think it's doing > anything too advanced. I'd be surprised if they caught any ZK regression > that wouldn't be well covered by the rest of your test infrastructure. > > -Todd > >> >> >> Patrick >> >> On Thu, Mar 6, 2014 at 7:48 AM, Flavio Junqueira <[email protected]> >> wrote: >> > +1, I have: >> > >> > - Checked signature and hashes >> > - Ran tests on Mac OS X, Windows, Linux Ubuntu >> > - Tested with internal application >> > >> > -Flavio >> > >> > On 25 Feb 2014, at 22:23, Mahadev Konar <[email protected]> wrote: >> > >> >> +1 >> >> >> >> Verified the signatures and the artifacts. >> >> >> >> thanks >> >> mahadev >> >> Mahadev Konar >> >> Hortonworks Inc. >> >> http://hortonworks.com/ >> >> >> >> >> >> On Mon, Feb 24, 2014 at 12:20 PM, Michi Mutsuzaki >> >> <[email protected]> wrote: >> >>> +1 >> >>> >> >>> ant test passed on ubuntu 12.04. >> >>> >> >>> On Sun, Feb 23, 2014 at 12:23 PM, Ted Yu <[email protected]> wrote: >> >>>> I pointed HBase 0.98 at 3.4.6 RC0 in the staging repo. >> >>>> I ran through test suite and it passed: >> >>>> >> >>>> [INFO] BUILD SUCCESS >> >>>> [INFO] >> >>>> >> >>>> ------------------------------------------------------------------------ >> >>>> [INFO] Total time: 1:09:42.116s >> >>>> [INFO] Finished at: Sun Feb 23 19:21:04 UTC 2014 >> >>>> [INFO] Final Memory: 48M/503M >> >>>> >> >>>> Cheers >> >>>> >> >>>> >> >>>> On Sun, Feb 23, 2014 at 11:39 AM, Flavio Junqueira >> >>>> <[email protected]>wrote: >> >>>> >> >>>>> This is a bugfix release candidate for 3.4.5. It fixes 117 issues, >> >>>>> including issues that affect >> >>>>> leader election, Zab, and SASL authentication. >> >>>>> >> >>>>> The full release notes is available at: >> >>>>> >> >>>>> >> >>>>> >> >>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310801&version=12323310 >> >>>>> >> >>>>> *** Please download, test and vote by March 9th 2014, 23:59 UTC+0. >> >>>>> *** >> >>>>> >> >>>>> Source files: >> >>>>> http://people.apache.org/~fpj/zookeeper-3.4.6-candidate-0/ >> >>>>> >> >>>>> Maven staging repo: >> >>>>> >> >>>>> >> >>>>> https://repository.apache.org/content/groups/staging/org/apache/zookeeper/zookeeper/3.4.6/ >> >>>>> >> >>>>> The tag to be voted upon: >> >>>>> https://svn.apache.org/repos/asf/zookeeper/tags/release-3.4.6-rc0 >> >>>>> >> >>>>> ZooKeeper's KEYS file containing PGP keys we use to sign the >> >>>>> release: >> >>>>> >> >>>>> http://www.apache.org/dist/zookeeper/KEYS >> >>>>> >> >>>>> Should we release this candidate? >> >>>>> >> >>>>> -Flavio >> >> >> >> -- >> >> CONFIDENTIALITY NOTICE >> >> NOTICE: This message is intended for the use of the individual or >> >> entity to >> >> which it is addressed and may contain information that is confidential, >> >> privileged and exempt from disclosure under applicable law. If the >> >> reader >> >> of this message is not the intended recipient, you are hereby notified >> >> that >> >> any printing, copying, dissemination, distribution, disclosure or >> >> forwarding of this communication is strictly prohibited. If you have >> >> received this communication in error, please contact the sender >> >> immediately >> >> and delete it from your system. Thank You. >> > > > > > > -- > Todd Lipcon > Software Engineer, Cloudera
