+1, let’s disable the test to unblock the release. On 7/27/16, 11:28 AM, "Balu Vellanki Bala" <bvella...@hortonworks.com> wrote:
>Thank you for testing Praveen. > >Hi Team, > >At this point we reached a point where scheduled instances are in WAITING >state on some machines and RUNNING successfully on other machines. This is >not related to Falcon code, but seems to be after the instance is >scheduled and accepted by workflow engine. > >I propose to disable these tests that depend on instances in external >components reaching a specific state. These code paths are also tested by >regression code. > >Please let me know if you agree. > >Thank you >Balu Vellanki > >On 7/27/16, 11:24 AM, "Praveen Adlakha" <praveen.adla...@inmobi.com> >wrote: > >>Hi All, >> >>Its consistently failing on machine as all the instances are in waiting >>state,so it through's a Null pointer Exception and code expects it to be >>in >>running state. >> >>Thanks >>Praveen >> >> >> >>On Wed, Jul 27, 2016 at 11:36 AM, Ying Zheng <yzh...@hortonworks.com> >>wrote: >> >>> I¹m able to build successfully on my laptop too. No UT and IT test >>>failure. >>> >>> Thanks, >>> Ying >>> >>> >>> On 7/26/16, 9:07 PM, "Peeyush Bishnoi" <bpeey...@yahoo.co.in.INVALID> >>> wrote: >>> >>> >Praveen, >>> >I am able to build Falcon from source without any issue. >>> >The respective IT ExtensionManagerIT has not failed for me and build >>>is >>> >successful. >>> >Thanks,---Peeyush >>> > >>> > On Tuesday, 26 July 2016 4:27 PM, Praveen Adlakha >>> ><praveen.adla...@inmobi.com> wrote: >>> > >>> > >>> > Hi Everyone, >>> > >>> >I did a build after removing my .m2 folder and building is failing on >>>: >>> > >>> >ExtensionManagerIT.testTrustedExtensionJob:120 NullPointer >>> > >>> >Also Falcon-1858 <https://issues.apache.org/jira/browse/FALCON-1858> >>>is a >>> >backward incompatible as we have changed the default settings, we have >>>not >>> >mentioned it in the release notes. >>> > >>> >Thanks >>> >Praveen >>> > >>> >On Tue, Jul 26, 2016 at 5:40 AM, Venkat Ranganathan < >>> >vranganat...@hortonworks.com> wrote: >>> > >>> >> Sending Balu¹s message as text so that the links are not mangled. >>> >> >>> >> Venkat >>> >> >>> >> On 7/25/16, 4:59 PM, "Balu Vellanki Bala" >>><bvella...@hortonworks.com> >>> >> wrote: >>> >> >>> >> Hello Everyone, >>> >> >>> >> >>> >> This is the call for vote for the following RC to be released as >>> >> official Apache Falcon 0.10 release. The source tar ball, signature >>>and >>> >> checksum files can be downloaded from >>> >> >>> >> >>> >>>https://dist.apache.org/repos/dist/dev/falcon/apache-falcon-0.10-sources >>>/ >>> >> >>> >> You can find the signing key here : >>> >> http://pgp.mit.edu/pks/lookup?op=vindex&search=0xF743ABF42E887C76 >>> >> You can find the KEYS file here: >>> >> https://dist.apache.org/repos/dist/release/falcon/KEYS >>> >> To verify signature: >>> >> gpg --verify apache-falcon-0.10-sources.tar.gz.asc >>> >> apache-falcon-0.10-sources.tar.gz >>> >> >>> >> Git tag commit-id for the release : release-0.10-rc0 >>> >> >>> >> >>> >> >>> >>>https://git-wip-us.apache.org/repos/asf?p=falcon.git;a=commit;h=91dc204b >>>6 >>> >>0c0403d16899a44d43ce3e22e9c9960 >>> >> >>> >> >>> >> We have closed around several JIRAs as part of this release, the >>> >> details of which can be found here: >>> >> >>> >> >>> >> >>> >>>https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12334758&; >>>s >>> >>tyleName=Html&projectId=12314429 >>> >> >>> >> Please find the release notes with brief explanation on key >>>changes >>> >>at >>> >> JIRA https://issues.apache.org/jira/browse/FALCON-2098 >>> >> >>> >> This vote will remain open for at least 72 hours. Please vote on >>> >> releasing this RC. >>> >> <https://issues.apache.org/jira/browse/FALCON-2098> >>> >> >>> >> [ ] +1 approve >>> >> [ ] +0 no opinion >>> >> [ ] -1 disapprove (and reason why) >>> >> >>> >> +1 from my side >>> >> >>> >> Thank you >>> >> Balu Vellanki >>> >> >>> >> >>> >> >>> >> >>> > >>> >-- >>> >_____________________________________________________________ >>> >The information contained in this communication is intended solely for >>> >the >>> >use of the individual or entity to whom it is addressed and others >>> >authorized to receive it. It may contain confidential or legally >>> >privileged >>> >information. If you are not the intended recipient you are hereby >>> >notified >>> >that any disclosure, copying, distribution or taking any action in >>> >reliance >>> >on the contents of this information is strictly prohibited and may be >>> >unlawful. If you have received this communication in error, please >>>notify >>> >us immediately by responding to this email and then delete it from >>>your >>> >system. The firm is neither liable for the proper and complete >>> >transmission >>> >of the information contained in this communication nor for any delay >>>in >>> >its >>> >receipt. >>> > >>> > >>> >>> >> >>-- >>_____________________________________________________________ >>The information contained in this communication is intended solely for >>the >>use of the individual or entity to whom it is addressed and others >>authorized to receive it. It may contain confidential or legally >>privileged >>information. If you are not the intended recipient you are hereby >>notified >>that any disclosure, copying, distribution or taking any action in >>reliance >>on the contents of this information is strictly prohibited and may be >>unlawful. If you have received this communication in error, please notify >>us immediately by responding to this email and then delete it from your >>system. The firm is neither liable for the proper and complete >>transmission >>of the information contained in this communication nor for any delay in >>its >>receipt. >
