You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@geode.apache.org by "Steve Sienkowski (Jira)" <ji...@apache.org> on 2020/01/29 20:43:00 UTC

[jira] [Created] (GEODE-7749) Transient CI Pipeline Failures

Steve Sienkowski created GEODE-7749:
---------------------------------------

             Summary: Transient CI Pipeline Failures
                 Key: GEODE-7749
                 URL: https://issues.apache.org/jira/browse/GEODE-7749
             Project: Geode
          Issue Type: Bug
            Reporter: Steve Sienkowski


Lately, there have been a number of transient CI Pipeline failures that are often resolved by restarting the failed job. 

One possible source for the increase in transient CI network/resource failures is the additional load of the native client develop pipeline.

 

https://concourse.gemfire-ci.info/teams/main/pipelines/gemfire-develop-test/jobs/VersioningHydraTest/builds/189#A

 
{code:java}
resource script '/opt/resource/in [/tmp/build/get]' failed: exit status 1{code}
 

[WindowsIntegrationTestOpenJDK11  #1197|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsIntegrationTestOpenJDK11/builds/1197]
{code:java}
Heavy lifter's Instance ID is: #################
timeout exceeded
{code}
 

Other's to be added as comments.

 

 

 



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