Jaydeep, Which test failed for you?
The oozie tests take a long time to run and usually package is built with skip tests. If the test failure is because of test issue, and doesn¹t point to any underlying code issue, we should go ahead with this release candidate Regards, Shwetha On 28/10/16, 12:46 AM, "Robert Kanter" <[email protected]> wrote: >Jaydeep, can you file a JIRA for the test failure? >I think it would be good to have clean tests for the release. > >thanks >- Robert > >On Thu, Oct 27, 2016 at 3:40 AM, jaydeep vishwakarma ><[email protected] >> wrote: > >> Verified the release candidate : >> >> - Signature looks good >> - Validated checksums >> - LICENSE looks ok. >> - Not able to built from source. Seeing a test failure. >> >> Regards, >> Jaydeep >> >> ---------- Forwarded message ---------- >> From: Abhishek Bafna <[email protected]> >> Date: Tue, Oct 25, 2016 at 11:08 AM >> Subject: [VOTE] Release Oozie 4.3.0 (candidate 0) >> To: [email protected] >> >> >> Hi, >> >> I have created a build for Oozie 4.3.0, candidate 0. >> >> Keys to verify the signature of the release artifact are available at >> >> http://www.apache.org/dist/oozie/KEYS >> >> Please download, test, and try it out: >> >> https://dist.apache.org/repos/dist/dev/oozie/oozie-4.3.0-rc0/ >> >> The release, md5 signature, gpg signature, and rat report can all >> be found at the above address. >> >> Vote closes on [Sat Oct 29 11:00:00 IST 2016]. >> >> Thanks! >> Abhishek Bafna >>
