[
https://issues.apache.org/jira/browse/BEAM-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16204133#comment-16204133
]
Valentyn Tymofieiev commented on BEAM-3056:
-------------------------------------------
I think I've seen this error in other precommit runs, where it manifested in a
different form:
2017-10-13T18:18:05.495 [INFO] Failsafe report directory:
/home/jenkins/jenkins-slave/workspace/beam_PreCommit_Java_MavenInstall/examples/java/target/failsafe-reports
2017-10-13T18:18:05.496 [INFO] parallel='all', perCoreThreadCount=true,
threadCount=4, useUnlimitedThreads=false, threadCountSuites=0,
threadCountClasses=0, threadCountMethods=0, parallelOptimized=true
2017-10-13T18:18:05.501 [INFO]
2017-10-13T18:18:05.502 [INFO]
-------------------------------------------------------
2017-10-13T18:18:05.502 [INFO] T E S T S
2017-10-13T18:18:05.502 [INFO]
-------------------------------------------------------
2017-10-13T19:20:43.301 [INFO] Running org.apache.beam.examples.WordCountIT
2017-10-13T19:20:43.737 [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped:
0, Time elapsed: 3,741.458 s <<< FAILURE! - in
org.apache.beam.examples.WordCountIT
2017-10-13T19:20:43.738 [ERROR]
testE2EWordCount(org.apache.beam.examples.WordCountIT) Time elapsed: 3,741.458
s <<< ERROR!
java.lang.RuntimeException: (1046f53a24282634): Workflow failed. Causes:
(1046f53a24282007): The Dataflow appears to be stuck. Please reach out to the
Dataflow team at
http://stackoverflow.com/questions/tagged/google-cloud-dataflow.
at
org.apache.beam.runners.dataflow.TestDataflowRunner.run(TestDataflowRunner.java:133)
at
org.apache.beam.runners.dataflow.TestDataflowRunner.run(TestDataflowRunner.java:89)
at
org.apache.beam.runners.dataflow.TestDataflowRunner.run(TestDataflowRunner.java:54)
at org.apache.beam.sdk.Pipeline.run(Pipeline.java:303)
at org.apache.beam.sdk.Pipeline.run(Pipeline.java:289)
at org.apache.beam.examples.WordCount.main(WordCount.java:188)
at
org.apache.beam.examples.WordCountIT.testE2EWordCount(WordCountIT.java:70)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at
org.apache.maven.surefire.junitcore.pc.Scheduler$1.run(Scheduler.java:393)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
> Java precommit tests on Jenkins run too slow, delaying commits.
> ---------------------------------------------------------------
>
> Key: BEAM-3056
> URL: https://issues.apache.org/jira/browse/BEAM-3056
> Project: Beam
> Issue Type: Bug
> Components: testing
> Reporter: Valentyn Tymofieiev
> Assignee: Jason Kuster
>
> Here's an example of two instances where the issue affected me in the last
> few days.
> The test suite consistently made progress, then timed out after 150 min.
> https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/15044/consoleFull
> https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/15037/consoleFull
> What are our options here, besides increasing the timeout?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
