Wangda:
In the meantime, you can find the failed unit test from console log. e.g.:

https://builds.apache.org/job/PreCommit-YARN-Build/5040/console

Then you can run the test locally to see if the failure was related to your
patch.

Cheers

On Fri, Sep 19, 2014 at 2:54 AM, Wangda Tan <wheele...@gmail.com> wrote:

> Hi Steve,
> I guess this problem should be also caused by wrong URL, if anybody have
> admin access to Jenkins, correct URL should be easily found.
>
> Thanks,
> Wangda
>
> On Fri, Sep 19, 2014 at 4:32 PM, Steve Loughran <ste...@hortonworks.com>
> wrote:
>
> > Looks like HADOOP-11084 isn't complete —the patch to the build to get it
> > working post-git
> >
> > before that patch the builds weren't working at all ... now its just
> > getting the URLs wrong.
> >
> > If you can work out the right URLs we can fix this easily enough
> >
> > On 19 September 2014 09:24, Wangda Tan <wheele...@gmail.com> wrote:
> >
> > > Hi Hadoop developers,
> > > I found recently, I cannot access Jenkins generated results, like:
> > >
> > >
> > >
> > > *Test
> > > results:
> > > https://builds.apache.org/job/PreCommit-YARN-Build/5039//testReport/
> > > <https://builds.apache.org/job/PreCommit-YARN-Build/5039//testReport/
> > > >Findbugs
> > > warnings:
> > >
> >
> https://builds.apache.org/job/PreCommit-YARN-Build/5039//artifact/PreCommit-HADOOP-Build-patchprocess/newPatchFindbugsWarningshadoop-yarn-client.html
> > > <
> > >
> >
> https://builds.apache.org/job/PreCommit-YARN-Build/5039//artifact/PreCommit-HADOOP-Build-patchprocess/newPatchFindbugsWarningshadoop-yarn-client.html
> > > >Javac
> > > warnings:
> > >
> >
> https://builds.apache.org/job/PreCommit-YARN-Build/5039//artifact/PreCommit-HADOOP-Build-patchprocess/diffJavacWarnings.txt
> > > <
> > >
> >
> https://builds.apache.org/job/PreCommit-YARN-Build/5039//artifact/PreCommit-HADOOP-Build-patchprocess/diffJavacWarnings.txt
> > > >*
> > >
> > > It will report 404 when trying to access findbugs/javac warnings and it
> > > will redirect to info page of build when trying to access test report.
> > >
> > > I'm not sure if there's any recent changes on Jenkins configuration.
> Did
> > > you hit the problem like this?
> > >
> > > Thanks,
> > > Wangda
> > >
> >
> > --
> > 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.
> >
>

Reply via email to