Thanks for your input Steve! --Yongjun
On Wed, Nov 19, 2014 at 1:45 AM, Steve Loughran <ste...@hortonworks.com> wrote: > If you have a change that spans the projects you need to submit a separate > JIRA for each one anyway, to give each team the ability to > review/accept/reject the patch > > On 18 November 2014 23:58, Ray Chiang <rchi...@cloudera.com> wrote: > > > I had to go back and look, but it was Akira Ajisaka that had recommended > it > > back when I ran into the issue: > > > > > > > https://issues.apache.org/jira/browse/HADOOP-10946?focusedCommentId=14108880&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14108880 > > > > Fortunately, my patch was easy to split up. > > > > -Ray > > > > > > On Tue, Nov 18, 2014 at 2:24 PM, Chris Nauroth <cnaur...@hortonworks.com > > > > wrote: > > > > > That's an interesting find. This has not always been the case. In the > > > past, we've provided consolidated patches on a HADOOP jira to get > > > pre-commit coverage when changes span multiple sub-projects. Yongjun, > if > > > you haven't already done so, I suggest filing a jira for this. > > > > > > Chris Nauroth > > > Hortonworks > > > http://hortonworks.com/ > > > > > > > > > On Sat, Nov 15, 2014 at 8:19 AM, Yongjun Zhang <yzh...@cloudera.com> > > > wrote: > > > > > > > For all's info, confirmed what Ray stated, indeed it's the reason! > > > > > > > > Thanks. > > > > > > > > --Yongjun > > > > > > > > > > > > On Fri, Nov 14, 2014 at 2:40 PM, Yongjun Zhang <yzh...@cloudera.com> > > > > wrote: > > > > > > > > > Many thanks Ray, good to know! > > > > > > > > > > --Yongjun > > > > > > > > > > On Fri, Nov 14, 2014 at 2:03 PM, Ray Chiang <rchi...@cloudera.com> > > > > wrote: > > > > > > > > > >> Your patch covers multiple projects (I see 81 files across > > > > >> hadoop-common-project, hadoop-hdfs-project, > > hadoop-mapreduce-project, > > > > >> hadoop-tools, hadoop-yarn-project). > > > > >> > > > > >> Jenkins had problems with that for me a few months back. If you > > break > > > > it > > > > >> up per-project, it should work just fine. > > > > >> > > > > >> -Ray > > > > >> > > > > >> > > > > >> On Fri, Nov 14, 2014 at 1:49 PM, Ted Yu <yuzhih...@gmail.com> > > wrote: > > > > >> > > > > >> > Adding builds@apache > > > > >> > > > > > >> > On Fri, Nov 14, 2014 at 1:34 PM, Yongjun Zhang < > > yzh...@cloudera.com > > > > > > > > >> > wrote: > > > > >> > > > > > >> > > Hi, > > > > >> > > > > > > >> > > One issue to report here, any help would be greatly > appreciated! > > > > >> > > > > > > >> > > I noticed that multiple patch submissions to > > > > >> > > https://issues.apache.org/jira/browse/HADOOP-11293 > > > > >> > > did not trigger jenkins test run. > > > > >> > > > > > > >> > > Thanks Chris Nauroth for the help to trigger one manually for > > me: > > > > >> > > > > > > >> > > https://builds.apache.org/job/PreCommit-HADOOP-Build/5079/ > > > > >> > > > > > > >> > > and it turned out the manually triggered one did not report > > result > > > > >> back > > > > >> > to > > > > >> > > the jira upon finishing. > > > > >> > > > > > > >> > > I submitted the same patch to another jira (HADOOP-11045) > that I > > > was > > > > >> > > working on, which triggered jenkins test before, and it seems > > not > > > > >> > > triggering this time too. > > > > >> > > > > > > >> > > So it looks like something is broken. This might be just a > > HADOOP > > > > jira > > > > >> > > issue (HDFS jira seems to be fine). > > > > >> > > > > > > >> > > Thanks a lot for looking into. > > > > >> > > > > > > >> > > --Yongjun > > > > >> > > > > > > >> > > > > > >> > > > > > > > > > > > > > > > > > > > > -- > > > 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. > > > > > > > -- > 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. >
