So the report publisher has '**/build/test-results/*.xml, **/build/test-results-flaky/*.xml' which should work. I am not sure why it is not picking up the flaky test failures, however, I did update to remove the space between the two patterns, '**/build/test-results/*.xml,**/build/test-results-flaky/*.xml'. I hope that will fix it, as maybe it was trimming the space at the beginning of the second pattern and using it as is.
I should note I updated both the release and nightly builds, as they have the same patterns. --Mark On Thu, Jul 28, 2016 at 11:56 AM, Dan Smith <dsm...@pivotal.io> wrote: > Also, the release branch jenkins job needs to pick up failures from this > flakyTest target because they are not showing up in the test results. Can > someone with access to jenkins fix that? > > -Dan > > On Thu, Jul 28, 2016 at 10:57 AM, Bruce Schuchardt <bschucha...@pivotal.io > > > wrote: > > > This is a problem in the geode-assembly build.gradle configuration. The > > flakyTest task needs to depend on the installed product, like > > distributedTest does. I've fixed that on the develop branch. > > > > > > Le 7/28/2016 à 10:45 AM, Apache Jenkins Server a écrit : > > > >> l.web.controllers.RestAPIsOnMembersFunctionExecutionDUnitTest > > >> testFunctionExecutionOnAllMembers FAILED > >> java.lang.AssertionError: unable to locate geode-web-api WAR file > >> > >> java.lang.NullPointerException > >> > > > > >
