[ 
https://issues.apache.org/jira/browse/GEODE-837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15322944#comment-15322944
 ] 

ASF subversion and git services commented on GEODE-837:
-------------------------------------------------------

Commit 11e637493d5f12aef53db98695d5b3e69315561c in incubator-geode's branch 
refs/heads/develop from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=11e6374 ]

GEODE-837: update eclipse formatter to match intellij formatter

* change profile name from GemFire to Geode
* update order of imports


> Jenkins is not picking up test results
> --------------------------------------
>
>                 Key: GEODE-837
>                 URL: https://issues.apache.org/jira/browse/GEODE-837
>             Project: Geode
>          Issue Type: Bug
>          Components: build
>            Reporter: Dan Smith
>            Assignee: Kirk Lund
>
> After c5efb80518abc2a2c7390af1d46e7c5892801e55, where we stopped searching 
> for specific test names, jenkins is no longer reporting dunit test results.
> The tests are still being run, but the XML reports that jenkins uses are 
> empty.
> I tracked the issue down partially. It looks like what is happening is the 
> dunit tests are running and reporting results, but then when the integration 
> tests run, it generates new XML files that overrwrite the dunit results in 
> gemfire-core/build/test-results with files that look like this (see how there 
> are no test results reported)
> {noformat}
> <testsuite name="com.gemstone.gemfire.test.dunit.tests.BasicDUnitTest" 
> tests="0" skipped="0" failures="0" errors="0" timestamp="1970-01-01T00:00:00" 
> hostname="dsmith-virtual" time="0.0">
> {noformat}
> It looks like this has something to do with the junit category stuff. Unit 
> tests files aren't getting stomped on like this, but dunit test files are. 
> Perhaps something to do with the DistributedTestCase hierarchy.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to