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

["Steve Sienkowski (Jira)" <ji...@apache.org>]

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

Steve Sienkowski commented on GEODE-7749:
-----------------------------------------

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




 
{code:java}
ERROR: (gcloud.compute.instances.create) Could not fetch resource:
10:43:42 - The resource 'projects/apachegeode-ci/zones/us-central1-a/instances/heavy-lifter-XXXXXXXXXXXX' already exists
{code}
 

> Transient CI Pipeline Failures
> ------------------------------
>
>                 Key: GEODE-7749
>                 URL: https://issues.apache.org/jira/browse/GEODE-7749
>             Project: Geode
>          Issue Type: Bug
>            Reporter: Steve Sienkowski
>            Priority: Major
>
> 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)