[
https://issues.apache.org/jira/browse/BEAM-14017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503923#comment-17503923
]
Daniel Oliveira commented on BEAM-14017:
----------------------------------------
I spent some time looking into this and couldn't figure out anything really
useful. The best lead I have is that the error that's appearing is probably due
to being unable to connect to a Kubernetes cluster, and that the error first
started appearing Feb. 25 sometime between 4 PM PST and 10 PM PST. It seems
likely that this is due to a change in our GCP environment but I haven't been
able to find what it could be.
Last good run:
https://ci-beam.apache.org/job/beam_PreCommit_CommunityMetrics_Cron/4794/
First bad run:
https://ci-beam.apache.org/job/beam_PreCommit_CommunityMetrics_Cron/4795/
> beam_PreCommit_CommunityMetrics_Cron is failing.
> ------------------------------------------------
>
> Key: BEAM-14017
> URL: https://issues.apache.org/jira/browse/BEAM-14017
> Project: Beam
> Issue Type: Bug
> Components: testing
> Reporter: Valentyn Tymofieiev
> Assignee: Heejong Lee
> Priority: P1
>
> https://ci-beam.apache.org/job/beam_PreCommit_CommunityMetrics_Cron/4805/console
> 10:14:48 > Task :beam-test-infra-metrics:validateConfiguration
> 10:14:48 W0228 18:14:48.092605 389274 helpers.go:549] --dry-run=true is
> deprecated (boolean value) and can be replaced with --dry-run=client.
> 10:15:20 Unable to connect to the server: dial tcp 104.154.102.21:443: i/o
> timeout (Client.Timeout exceeded while awaiting headers)
> 10:15:20
> 10:15:20 > Task :beam-test-infra-metrics:validateConfiguration FAILED
> 10:15:20
> 10:15:20 FAILURE: Build failed with an exception.
> 10:15:20
> 10:15:20 * What went wrong:
> 10:15:20 Execution failed for task
> ':beam-test-infra-metrics:validateConfiguration'.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
