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

Daniel Oliveira commented on BEAM-11499:
----------------------------------------

I ran into this issue again in some unrelated work and once again it happened 
when building a java container in a repo that hadn't been "gradle clean"ed. 
Looks like the presence of old vendored files in the Java code causes this 
issue.

In an in-progress PR (https://github.com/apache/beam/pull/14030) I'm adding the 
Java docker container as a prerequisite because it was missing. I think a good 
further improvement could be to modify the gradle tasks for running the ULR 
integration test to require gradle clean as a requirement, so it will be 
guaranteed to run in a clean environment.

If I ever find out what exactly causes the hang I'll also try to add a way to 
catch it and throw an error so it's actually debug-able instead of just 
mysteriously hanging.

> ULR cross-language integration tests in Go SDK timing out
> ---------------------------------------------------------
>
>                 Key: BEAM-11499
>                 URL: https://issues.apache.org/jira/browse/BEAM-11499
>             Project: Beam
>          Issue Type: Bug
>          Components: cross-language, sdk-go
>            Reporter: Daniel Oliveira
>            Assignee: Daniel Oliveira
>            Priority: P2
>
> Configuration:
> * Go Pipelines
> * Python Portable Runner
> * Java Test Expansion Service
> Times out right now on the Combine test. There's a pretty large stack trace 
> for all goroutines afterwards, but none of them show any obvious issues. 
> Can't see which other XLang tests it fails on because the timeout causes it 
> to abort running any subsequent tests.



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

Reply via email to