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

Robert Burke commented on BEAM-9815:
------------------------------------

I'm going to stop looking at this point, but the open source side seems to be 
exhausted. The code eventually runs a binary on the Dataflow side to set up an 
artifact service, that [proxies reading from 
GCS](https://github.com/apache/beam/blob/24361d1b5981ef7d18e586a8e5deaf683f4329f1/sdks/go/pkg/beam/artifact/gcsproxy/retrieval.go#L82).
 That code 

is in the [artifact 
package](https://github.com/apache/beam/blob/24361d1b5981ef7d18e586a8e5deaf683f4329f1/sdks/go/pkg/beam/artifact/materialize.go#L135)
 though it's called from something inside google. That there might have some 
kind of version skew with the container/boot.go code, and need updating on the 
google side. I'm unable to figure that one out at this time.


> beam_PostCommit_Go perma red due to failing to start container
> --------------------------------------------------------------
>
>                 Key: BEAM-9815
>                 URL: https://issues.apache.org/jira/browse/BEAM-9815
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-go, test-failures
>            Reporter: Chamikara Madhusanka Jayalath
>            Assignee: Robert Bradshaw
>            Priority: Critical
>              Labels: currently-failing
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> For example,
> [https://builds.apache.org/job/beam_PostCommit_Go/6847/]
> [https://pantheon.corp.google.com/logs/viewer?project=apache-beam-testing&folder&organizationId&minLogLevel=500&expandAll=false&timestamp=2020-04-24T15:09:13.455000000Z&customFacets=&limitCustomFacetWidth=true&interval=NO_LIMIT&resource=dataflow_step%2Fjob_id%2F2020-04-24_05_03_49-5495819388067192698&scrollTimestamp=2020-04-24T13:03:38.313084000Z]



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

Reply via email to