You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Amit Sela (JIRA)" <ji...@apache.org> on 2016/03/18 18:35:33 UTC

[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&focusedCommentId=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)