[
https://issues.apache.org/jira/browse/GEODE-8987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17293266#comment-17293266
]
ASF GitHub Bot commented on GEODE-8987:
---------------------------------------
lgtm-com[bot] commented on pull request #6073:
URL: https://github.com/apache/geode/pull/6073#issuecomment-788470269
This pull request **introduces 1 alert** when merging
b79a76001c740b8e8f18c8b1d2ebf80979855e53 into
77e6a0475556a12dd70ee9e3dda6f558887bc164 - [view on
LGTM.com](https://lgtm.com/projects/g/apache/geode/rev/pr-334d7fe26f789ff9e906f0b8e2bd7015367343d1)
**new alerts:**
* 1 for Useless null check
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> 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)
