>From https://builds.apache.org/job/Hadoop-hdfs-trunk/1854/console :

ERROR: No artifacts found that match the file pattern
"trunk/hadoop-hdfs-project/*/target/*.tar.gz". Configuration
error?ERROR <http://stacktrace.jenkins-ci.org/search?query=ERROR>:
?trunk/hadoop-hdfs-project/*/target/*.tar.gz? doesn?t match anything,
but ?hadoop-hdfs-project/*/target/*.tar.gz? does. Perhaps that?s what
you mean?


I corrected the path to hdfs tar ball.


FYI



On Fri, Aug 29, 2014 at 8:48 AM, Alejandro Abdelnur <t...@cloudera.com>
wrote:

> it seems we missed updating the HADOOP precommit job to use Git, it was
> still using SVN. I've just updated it.
>
> thx
>
>
> On Thu, Aug 28, 2014 at 9:26 PM, Ted Yu <yuzhih...@gmail.com> wrote:
>
> > Currently patchprocess/ (contents shown below) is one level higher than
> > ${WORKSPACE}
> >
> > diffJavadocWarnings.txt         newPatchFindbugsWarningshadoop-hdfs.html
> >  patchFindBugsOutputhadoop-hdfs.txt    patchReleaseAuditOutput.txt
> >  trunkJavadocWarnings.txt
> > filteredPatchJavacWarnings.txt  newPatchFindbugsWarningshadoop-hdfs.xml
> > patchFindbugsWarningshadoop-hdfs.xml  patchReleaseAuditWarnings.txt
> > filteredTrunkJavacWarnings.txt  patch
> > patchJavacWarnings.txt                testrun_hadoop-hdfs.txt
> > jira                            patchEclipseOutput.txt
> >  patchJavadocWarnings.txt              trunkJavacWarnings.txt
> >
> > Under Files to archive input box of PreCommit-HDFS-Build/configure, I
> saw:
> >
> > ‘../patchprocess/*’ doesn’t match anything, but ‘*’ does. Perhaps that’s
> > what you mean?
> >
> > I guess once patchprocess is moved back under ${WORKSPACE}, a lot of
> things
> > would be back to normal.
> >
> > Cheers
> >
> > On Thu, Aug 28, 2014 at 9:16 PM, Alejandro Abdelnur <t...@cloudera.com>
> > wrote:
> >
> > > i'm also seeing broken links for javadocs warnings.
> > >
> > > Alejandro
> > > (phone typing)
> > >
> > > > On Aug 28, 2014, at 20:00, Andrew Wang <andrew.w...@cloudera.com>
> > wrote:
> > > >
> > > > I noticed that the JUnit test results aren't getting picked up
> > anymore. I
> > > > suspect we just need to update the path to the surefire output, but
> > based
> > > > on a quick examination I'm not sure what that is.
> > > >
> > > > Does someone mind taking another look?
> > > >
> > > >
> > > > On Thu, Aug 28, 2014 at 4:21 PM, Karthik Kambatla <
> ka...@cloudera.com>
> > > > wrote:
> > > >
> > > >> Thanks Giri and Ted for fixing the builds.
> > > >>
> > > >>
> > > >>> On Thu, Aug 28, 2014 at 9:49 AM, Ted Yu <yuzhih...@gmail.com>
> wrote:
> > > >>>
> > > >>> Charles:
> > > >>> QA build is running for your JIRA:
> > > >>>
> https://builds.apache.org/job/PreCommit-hdfs-Build/7828/parameters/
> > > >>>
> > > >>> Cheers
> > > >>>
> > > >>>
> > > >>>> On Thu, Aug 28, 2014 at 9:41 AM, Charles Lamb <cl...@cloudera.com
> >
> > > >>> wrote:
> > > >>>
> > > >>>>> On 8/28/2014 12:07 PM, Giridharan Kesavan wrote:
> > > >>>>>
> > > >>>>> Fixed all the 3 pre-commit buids. test-patch's git reset --hard
> is
> > > >>>>> removing
> > > >>>>> the patchprocess dir, so moved it off the workspace.
> > > >>>> Thanks Giri. Should I resubmit HDFS-6954's patch? I've gotten 3
> or 4
> > > >>>> jenkins messages that indicated the problem so something is
> > > >> resubmitting,
> > > >>>> but now that you've fixed it, should I resubmit it again?
> > > >>>>
> > > >>>> Charles
> > > >>
> > >
> >
>
>
>
> --
> Alejandro
>

Reply via email to