[
https://issues.apache.org/jira/browse/GEODE-7505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16983718#comment-16983718
]
Bill Burcham commented on GEODE-7505:
-------------------------------------
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-develop-main/1.12.0-SNAPSHOT.0053/test-results/distributedTest/1574806317/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
http://files.apachegeode-ci.info/builds/apache-develop-main/1.12.0-SNAPSHOT.0053/test-artifacts/1574806317/distributedtestfiles-OpenJDK11-1.12.0-SNAPSHOT.0053.tgz
> CI Failure: DistributedTestOpenJDK11 Timed Out (Hang/Hung)
> ----------------------------------------------------------
>
> Key: GEODE-7505
> URL: https://issues.apache.org/jira/browse/GEODE-7505
> Project: Geode
> Issue Type: Bug
> Components: tests
> Reporter: Bill Burcham
> Priority: Major
>
> This build timed out while running DUnit tests:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/1319
> From the artifacts ({{dunit-hangs.txt}}) it appears it was running
> {{org.apache.geode.test.dunit.examples.InvokeRunnableExampleTest
> invokeHelloWorldForEachVMInGetAllVMs}} when it timed out
> The previous build passed all DUnit tests:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/1318
> but we don't have artifacts for that one because we were having Concourse
> infrastructure problems
> But the only commit between those two builds is this one:
> {noformat}
> Author: Alberto Bustamante Reyes <alb3rt...@users.noreply.github.com>
> Date: Wed Oct 9 17:32:16 2019 +0200
> GEODE-2184: Genericize Java version numbers in docs
> commit 883a4211b6189448482737d858c4ed9ce875f3e2
> {noformat}
> I see no reason why documentation changes would cause a regression that would
> cause a new hang. My theory is that this is either an infrastructure issue
> e.g. transient networking problem, or it's caused by an old test or product
> fault.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
