[jira] [Commented] (BEAM-133) Test flakiness in the Spark runner
[
https://issues.apache.org/jira/browse/BEAM-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15201826#comment-15201826
]
Amit Sela commented on BEAM-133:
Definitely an infrastructure issue.
You can see in the console output that in builds that failed the Spark runner
build tries to download from the MapR repository:
[INFO] Building Spark Beam Runner 0.4.3-SNAPSHOT
[INFO]
[INFO] Downloading:
http://repository.mapr.com/maven/com/mapr/mapr-root/2.0-SNAPSHOT/maven-metadata.xml
[INFO] Downloading:
> Test flakiness in the Spark runner
> --
>
> Key: BEAM-133
> URL: https://issues.apache.org/jira/browse/BEAM-133
> Project: Beam
> Issue Type: Bug
> Components: runner-spark
>Reporter: Davor Bonaci
>Assignee: Amit Sela
>
> Jenkins shows some flakiness in the Spark runner in the context of an
> unrelated pre-commit test.
> {code}
> Results :
> Tests in error:
> AvroPipelineTest.testGeneric:75 » Runtime java.io.IOException: Could
> not creat...
> NumShardsTest.testText:77 » Runtime java.io.IOException: Could not
> create File...
> HadoopFileFormatPipelineTest.testSequenceFile:83 » Runtime
> java.io.IOException...
>
> TransformTranslatorTest.testTextIOReadAndWriteTransforms:76->runPipeline:96 »
> Runtime
> KafkaStreamingTest.testRun:121 » Runtime java.io.IOException: failure
> to login...
> Tests run: 27, Failures: 0, Errors: 5, Skipped: 0
> [ERROR] There are test failures.
> {code}
> https://builds.apache.org/job/beam_PreCommit/98/console
> Amit, does this sounds like a test code issue or the infrastructure issue?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (BEAM-133) Test flakiness in the Spark runner
[
https://issues.apache.org/jira/browse/BEAM-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15202292#comment-15202292
]
Davor Bonaci commented on BEAM-133:
---
Marking resolved for now.
> Test flakiness in the Spark runner
> --
>
> Key: BEAM-133
> URL: https://issues.apache.org/jira/browse/BEAM-133
> Project: Beam
> Issue Type: Bug
> Components: project-management
>Reporter: Davor Bonaci
>Assignee: Davor Bonaci
>
> Jenkins shows some flakiness in the Spark runner in the context of an
> unrelated pre-commit test.
> {code}
> Results :
> Tests in error:
> AvroPipelineTest.testGeneric:75 » Runtime java.io.IOException: Could
> not creat...
> NumShardsTest.testText:77 » Runtime java.io.IOException: Could not
> create File...
> HadoopFileFormatPipelineTest.testSequenceFile:83 » Runtime
> java.io.IOException...
>
> TransformTranslatorTest.testTextIOReadAndWriteTransforms:76->runPipeline:96 »
> Runtime
> KafkaStreamingTest.testRun:121 » Runtime java.io.IOException: failure
> to login...
> Tests run: 27, Failures: 0, Errors: 5, Skipped: 0
> [ERROR] There are test failures.
> {code}
> https://builds.apache.org/job/beam_PreCommit/98/console
> Amit, does this sounds like a test code issue or the infrastructure issue?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (BEAM-133) Test flakiness in the Spark runner
[
https://issues.apache.org/jira/browse/BEAM-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15201831#comment-15201831
]
Amit Sela commented on BEAM-133:
I guess our Jenkins uses multiple instances / machines, does it ?
If so, can we check if the failure is on the same one ?
Anyway it's a cache issue.
> Test flakiness in the Spark runner
> --
>
> Key: BEAM-133
> URL: https://issues.apache.org/jira/browse/BEAM-133
> Project: Beam
> Issue Type: Bug
> Components: runner-spark
>Reporter: Davor Bonaci
>Assignee: Amit Sela
>
> Jenkins shows some flakiness in the Spark runner in the context of an
> unrelated pre-commit test.
> {code}
> Results :
> Tests in error:
> AvroPipelineTest.testGeneric:75 » Runtime java.io.IOException: Could
> not creat...
> NumShardsTest.testText:77 » Runtime java.io.IOException: Could not
> create File...
> HadoopFileFormatPipelineTest.testSequenceFile:83 » Runtime
> java.io.IOException...
>
> TransformTranslatorTest.testTextIOReadAndWriteTransforms:76->runPipeline:96 »
> Runtime
> KafkaStreamingTest.testRun:121 » Runtime java.io.IOException: failure
> to login...
> Tests run: 27, Failures: 0, Errors: 5, Skipped: 0
> [ERROR] There are test failures.
> {code}
> https://builds.apache.org/job/beam_PreCommit/98/console
> Amit, does this sounds like a test code issue or the infrastructure issue?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (BEAM-133) Test flakiness in the Spark runner
[
https://issues.apache.org/jira/browse/BEAM-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15202273#comment-15202273
]
Jason Kuster commented on BEAM-133:
---
We've changed the Jenkins projects to use a Maven repository local to the
workspace. This should fix the problem; please let us know if it does not.
> Test flakiness in the Spark runner
> --
>
> Key: BEAM-133
> URL: https://issues.apache.org/jira/browse/BEAM-133
> Project: Beam
> Issue Type: Bug
> Components: project-management
>Reporter: Davor Bonaci
>Assignee: Davor Bonaci
>
> Jenkins shows some flakiness in the Spark runner in the context of an
> unrelated pre-commit test.
> {code}
> Results :
> Tests in error:
> AvroPipelineTest.testGeneric:75 » Runtime java.io.IOException: Could
> not creat...
> NumShardsTest.testText:77 » Runtime java.io.IOException: Could not
> create File...
> HadoopFileFormatPipelineTest.testSequenceFile:83 » Runtime
> java.io.IOException...
>
> TransformTranslatorTest.testTextIOReadAndWriteTransforms:76->runPipeline:96 »
> Runtime
> KafkaStreamingTest.testRun:121 » Runtime java.io.IOException: failure
> to login...
> Tests run: 27, Failures: 0, Errors: 5, Skipped: 0
> [ERROR] There are test failures.
> {code}
> https://builds.apache.org/job/beam_PreCommit/98/console
> Amit, does this sounds like a test code issue or the infrastructure issue?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (BEAM-133) Test flakiness in the Spark runner
[
https://issues.apache.org/jira/browse/BEAM-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15201834#comment-15201834
]
Davor Bonaci commented on BEAM-133:
---
Acknowledged. I'll take this over.
> Test flakiness in the Spark runner
> --
>
> Key: BEAM-133
> URL: https://issues.apache.org/jira/browse/BEAM-133
> Project: Beam
> Issue Type: Bug
> Components: runner-spark
>Reporter: Davor Bonaci
>Assignee: Davor Bonaci
>
> Jenkins shows some flakiness in the Spark runner in the context of an
> unrelated pre-commit test.
> {code}
> Results :
> Tests in error:
> AvroPipelineTest.testGeneric:75 » Runtime java.io.IOException: Could
> not creat...
> NumShardsTest.testText:77 » Runtime java.io.IOException: Could not
> create File...
> HadoopFileFormatPipelineTest.testSequenceFile:83 » Runtime
> java.io.IOException...
>
> TransformTranslatorTest.testTextIOReadAndWriteTransforms:76->runPipeline:96 »
> Runtime
> KafkaStreamingTest.testRun:121 » Runtime java.io.IOException: failure
> to login...
> Tests run: 27, Failures: 0, Errors: 5, Skipped: 0
> [ERROR] There are test failures.
> {code}
> https://builds.apache.org/job/beam_PreCommit/98/console
> Amit, does this sounds like a test code issue or the infrastructure issue?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
