Ted and other folks, sorry to bother you again. I must miss something here about how to get the javadoc warning info.
The hadoop-QA result ( https://issues.apache.org/jira/browse/HBASE-9047?focusedCommentId=13816377&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13816377) shows ".. -1 javadoc. The javadoc tool appears to have generated 1 warning messages." but I am having trouble to figure out where to find the warning message. The closest thing is from the console output : ====================================================================== ====================================================================== Determining number of patched javadoc warnings. ====================================================================== ====================================================================== /home/jenkins/tools/maven/latest/bin/mvn clean package javadoc:javadoc -DskipTests -DHBasePatchProcess > /home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/patchprocess/patchJavadocWarnings.txt 2>&1 There appear to be 3 javadoc warnings generated by the patched build. " but it also doesn't show the warning message(is there a link to file patchJavadocWarnings.txt?) I also ran the 'test-patch.sh' locally, which didn't encounter additional javadoc warning. Thanks for your help in advance. Demai On Thu, Nov 7, 2013 at 10:52 AM, Demai Ni <[email protected]> wrote: > Ted, yeah. I think the -1 core test may be unrelated. > > also just saw that St.Ack resubmitted the patch. Many thanks to both of > you. > > > On Thu, Nov 7, 2013 at 9:25 AM, Ted Yu <[email protected]> wrote: > >> If you are concerned about the following from QA report: >> bq. -1 core tests. The patch failed these unit tests: >> >> You can always re-submit the latest patch to see if the test failure was >> reproducible (I assume you have run replication-related tests locally). >> >> >> On Thu, Nov 7, 2013 at 9:15 AM, Demai Ni <[email protected]> wrote: >> >> > Ted, thank you so much for the tips. It helps me to save a lot of time >> and >> > avoid to overuse the system. Appreciate it. ... Demai >> > >> > >> > On Thu, Nov 7, 2013 at 8:57 AM, Ted Yu <[email protected]> wrote: >> > >> > > From https://builds.apache.org/job/PreCommit-HBASE-Build/ , you can >> see >> > > that results from the last 15 QA runs were kept. >> > > There are many patches submitted everyday. Each QA result would be >> kept >> > > shorter than 24 hours. >> > > >> > > If you're investigating javadoc / findbugs warnings, you can find the >> > > respective command from dev-support/test-patch.sh >> > > >> > > Cheers >> > > >> > > >> > > On Thu, Nov 7, 2013 at 8:39 AM, Demai Ni <[email protected]> wrote: >> > > >> > > > hi, folks, >> > > > >> > > > sorry for asking the native question. I ran a Hadoop-QA yesterday >> > > > afternoon, and thought the result will be on the server for 24 >> hours. >> > > > However, it isn't available anymore (~12 hours) >> > > > >> > > > It is for hbase-9047, and this is link of the result. >> > > > >> https://builds.apache.org/job/PreCommit-HBASE-Build/7762//testReport/ >> > > > >> > > > Was there a recent change? or I was wrong about the 24 hour period? >> > > > >> > > > I know it is a 'stupid' question. well, I better understand it now, >> > then >> > > > 'abuse' the testing system. Many thanks. >> > > > >> > > > Demai >> > > > >> > > >> > >> > >
