[
https://issues.apache.org/jira/browse/GEODE-7749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Sienkowski updated GEODE-7749:
------------------------------------
Description:
Lately, there have been a number of transient CI Pipeline failures that are
often resolved by restarting the failed job.
[https://status.cloud.google.com/incident/compute/20001]
{code:java}
Google Compute Engine Incident #20001The issue with instance DELETE and STOP
operations in Google Compute Engine has been mitigated.Incident began at
2020-01-28 12:1{code}
{code:java}
We are experiencing an issue with stopping and deleting Google Compute Engine
instances affecting mainly us-central1-a, with a subset of global operations
impacted as well, the majority of which are
projects.setCommonInstanceMetadataInstance operations.
{code}
Failed jobs:
[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.
was:
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.
> Transient CI Pipeline Network and Resource Issues
> -------------------------------------------------
>
> 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.
> [https://status.cloud.google.com/incident/compute/20001]
>
> {code:java}
> Google Compute Engine Incident #20001The issue with instance DELETE and STOP
> operations in Google Compute Engine has been mitigated.Incident began at
> 2020-01-28 12:1{code}
> {code:java}
> We are experiencing an issue with stopping and deleting Google Compute Engine
> instances affecting mainly us-central1-a, with a subset of global operations
> impacted as well, the majority of which are
> projects.setCommonInstanceMetadataInstance operations.
> {code}
>
>
> Failed jobs:
>
> [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)
