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

Geode Integration commented on GEODE-8987:
------------------------------------------

Seen in [DistributedTestOpenJDK8 
#40|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/40]
 ... see [test 
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0021/test-results/distributedTest/1614410507/]
 or download 
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0021/test-artifacts/1614410507/distributedtestfiles-OpenJDK8-1.15.0-build.0021.tgz].

> CI Failure: Mass failures in DUnit tests following GEODE-8905
> -------------------------------------------------------------
>
>                 Key: GEODE-8987
>                 URL: https://issues.apache.org/jira/browse/GEODE-8987
>             Project: Geode
>          Issue Type: Bug
>    Affects Versions: 1.15.0
>            Reporter: Donal Evans
>            Priority: Major
>              Labels: pull-request-available
>
> Following the merging of GEODE-8905, both the DistrubutedTestOpenJDK11 and 
> DistributedTestOpenJDK8 CI jobs have been seeing very large numbers of failed 
> tests. Starting from 
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/41|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/41]
>  and 
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/39|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/39]
>  almost all subsequent runs have failed due to multiple connection, gradle 
> and other issues. It's unclear what the cause is at this time



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to