Hi Alan, Thanks for the review and comments.
For the test cases failure: It is the timing issue. Sometime it depends on the load of the machine too. Anyway there are multiple ways to make the test cases succeed: 1. Quicker approach: Run only the failed test case. such as "mvn ..... -Dtest=TestLauncher -Doozie.test.waitfor.ratio=4" 2. For whole test suites: "mvn ... -Doozie.test.waitfor.ratio=4" Regards, Mohammad ----- Original Message ----- From: Alan Gates <[email protected]> To: [email protected] Cc: oozie-dev <[email protected]> Sent: Tuesday, February 14, 2012 11:13 AM Subject: Re: [VOTE] Release Oozie 3.1.3 (candidate 2) +1 Checked out the LICENSE, NOTICE, DISCLAIMER, and readme.txt files. They all look good. I compiled and ran the tests. I did see one test failure in the unit tests (org.apache.oozie.action.hadoop.TestLauncher failed). I'll let you decide if that's a show stopper or not. Alan. On Feb 13, 2012, at 4:43 PM, Mohammad Islam wrote: > Hi, > > Thanks everyone for giving valuable comments for the RC0 and RC1. > > I created a new candidate (RC2) build for Oozie-3.1.3 incorporating most of > the comments (including Chris's finding). > The following JIRAs were resolved based on the comments: > > OOZIE-694 Update the Install and Quick start guide with appropriate hadoop > versions for branch-3.1 (Mohammad) > OOZIE-602 Update the Hadoop version to be an Apache Hadoop version (tucu) > OOZIE-689 XTestCase proxyuser settings fails with Hadoop 1.0.0/0.23.1 (tucu) > OOZIE-601 Oozie's POMs should use org.apache.oozie as group (tucu) > OOZIE-685 Update License file with 3rd party license information. (Mohammad) > OOZIE-682 Update version 3.1.3 to 3.1.3-incubating in all pom.xml.(Mohammad) > OOZIE-683 Add DISCLAIMER file in the root.(Mohammad) > OOZIE-681 Update readme.txt contents.(Mohammad) > OOZIE-680 oozie's assembly creates an extra level of empty subdirectory for > docs. (rvs via tucu) > OOZIE-608 testCoordChangeEndTime and testCoordChangeXCommand are > failing(Mohamed). > OOZIE-678 Update NOTICE.txt to reflect the workcount binaries into oozie > src(Mohammad) > > Keys used to sign the release are available at > http://svn.apache.org/viewvc/incubator/oozie/trunk/KEYS?view=markup. > > Please download, test, and try it out from here: > > http://people.apache.org/~kamrul/oozie-3.1.3-incubating-candidate-2/ > > The release log, md5 signature, gpg signature, and rat report all can be > found at the above link. > In case, anyone is interested, the svn tag from the release was created could > be found at : > https://svn.apache.org/repos/asf/incubator/oozie/tags/release-3.1.3-rc2/ > > Should we release this? Vote closes on Feb 15th. > > Regards, > Mohammad
