finally, could take a look at the (133) test errors, they're mostly caused by:
org.apache.wiki.TestEngine.firePageEvent(ILjava/lang/String;)V java.lang.NoSuchMethodError: org.apache.wiki.TestEngine.firePageEvent(ILjava/lang/String;)V at org.apache.wiki.TestEngine.deleteTestPage(TestEngine.java:250) at org.apache.wiki.plugin.ReferringPagesPluginTest.tearDown(ReferringPagesPluginTest.java:68) looking at jenkins logs, it seems that "ant sonar" is executed at analysis.a.o, but the changes to WikiEngine/TestEngine haven't been brought up. I'm adding depends="clean" to sonar-bootstrap target, that should do the trick (there are also 5 test failures, don't know yet if they fail b/c of the above or b/c of something related to the environment, we should see it in the next build) br, juan pablo On Sun, Dec 9, 2012 at 10:29 PM, Juan Pablo Santos Rodríguez < [email protected]> wrote: > Hi, > > latest commit should allow us to see tests failures through Sonar. I've > also filed https://issues.apache.org/jira/browse/INFRA-5619 to request > that e-mail notifications are sent from builds.a.o instead of > analysis.a.o/jenkins (the latter now is going to send always build success). > > > br, > juan pablo > > > > On Sun, Dec 9, 2012 at 4:55 PM, Juan Pablo Santos Rodríguez < > [email protected]> wrote: > >> Hi, >> >> the build at builds.a.o is also building fine, so it seems to me that the >> building failure is due to something specific to analysis.a.o, which is >> meant to feed the Sonar instance, maybe something related to execution >> order :-? We could request the junit report file to infra, but I think that >> the best approach here would be to enable a flag to continue the build >> despite failing tests, and then file a JIRA to infra to add this new >> property to the build at analysis.a.o (and while at it, wipe out the build >> workspace, just in case). >> >> At least this way we could see through Sonar why those tests have failed >> (it outputs the same information as the junit report file) without having >> to ask infra for the report every time. >> >> I'll try to have this change this evening/night and the appropiate JIRA >> for infra. >> >> >> br, >> juan pablo >> >> >> On Sun, Dec 9, 2012 at 2:33 PM, Glen Mazza <[email protected]> wrote: >> >>> Building with JDK 7.0, I'm just seeing one failure, in WikiEngineTest, >>> but that's due to some local changes I've put in trying to find a solution >>> for a open JIRA item. >>> >>> Glen >>> >>> >>> On 12/09/2012 06:19 AM, Harry Metske wrote: >>> >>>> Well there was some code change (yesterday). And although the build on >>>> my >>>> own laptop succeeded yesterday before I committed, the one at >>>> analysis.apache.org fails: >>>> >>>> The console output at [1] is telling that. these are the failing ones: >>>> [junit] Test org.apache.wiki.attachment.**AttachmentManagerTest >>>> FAILED >>>> [junit] Test org.apache.wiki.content.**PageRenamerTest FAILED >>>> [junit] Test org.apache.wiki.dav.**AttachmentDavProviderTest >>>> FAILED >>>> [junit] Test org.apache.wiki.dav.**HTMLPagesDavProviderTest FAILED >>>> [junit] Test org.apache.wiki.dav.**RawPagesDavProviderTest FAILED >>>> [junit] Test org.apache.wiki.parser.**JSPWikiMarkupParserTest >>>> FAILED >>>> [junit] Test org.apache.wiki.plugin.**InsertPageTest FAILED >>>> [junit] Test org.apache.wiki.plugin.**PageViewPluginTest FAILED >>>> [junit] Test org.apache.wiki.plugin.**RecentChangesPluginTest >>>> FAILED >>>> [junit] Test org.apache.wiki.plugin.**ReferringPagesPluginTest >>>> FAILED >>>> [junit] Test org.apache.wiki.plugin.**UndefinedPagesPluginTest >>>> FAILED >>>> [junit] Test org.apache.wiki.providers.** >>>> BasicAttachmentProviderTest >>>> FAILED >>>> [junit] Test org.apache.wiki.providers.**CachingProviderTest >>>> FAILED >>>> [junit] Test org.apache.wiki.render.**WysiwygEditingRendererTest >>>> FAILED >>>> [junit] Test org.apache.wiki.search.**SearchManagerTest FAILED >>>> [junit] Test org.apache.wiki.xmlrpc.**RPCHandlerTest FAILED >>>> >>>> It also tells that the more detailed output is at >>>> /x1/jenkins/jenkins-master/**jenkins-home/jobs/jspwiki/** >>>> workspace/tests/reports/junit-**noframes.html, >>>> but I have no idea how to get that (I am not allowed to login at >>>> analysis.apache.org). >>>> >>>> Anyone else ideas ? >>>> >>>> HArry >>>> >>>> >>>> [1] - >>>> https://analysis.apache.org/**jenkins/job/jspwiki/27/console<https://analysis.apache.org/jenkins/job/jspwiki/27/console> >>>> >>>> >>>> On 9 December 2012 11:36, Florian Holeczek <[email protected]> wrote: >>>> >>>> Any idea why the build is failing sometimes? Once this seems to even >>>>> have >>>>> changed without any change in the code base (!?) >>>>> Juan Pablo? >>>>> >>>>> Regards >>>>> Florian >>>>> >>>>> >>>>> -------- Original-Nachricht -------- >>>>> Betreff: jspwiki - Build # 27 - Still Failing! >>>>> Datum: Sun, 9 Dec 2012 01:59:48 +0000 (UTC) >>>>> Von: [email protected] >>>>> Antwort an: [email protected].****org< >>>>> jspwiki-dev@incubator.**apache.org <[email protected]>> >>>>> An: jspwiki-commits@incubator.**ap**ache.org <http://apache.org>< >>>>> jspwiki-commits@**incubator.apache.org<[email protected]> >>>>> >, >>>>> [email protected] >>>>> >>>>> >>>>> jspwiki - Build # 27 - Still Failing: >>>>> >>>>> Check console output at https://analysis.apache.org/** >>>>> jenkins/job/jspwiki/27/<https:**//analysis.apache.org/jenkins/** >>>>> job/jspwiki/27/ <https://analysis.apache.org/jenkins/job/jspwiki/27/>>to >>>>> view the results. >>>>> >>>>> >>>>> >>>>> >>> >> >
