You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Sam Rohde (JIRA)" <ji...@apache.org> on 2019/01/03 23:53:00 UTC

[jira] [Commented] (BEAM-5954) [Flake][Go PostCommit] Multiple Go Dataflow integration tests flaking.

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

Sam Rohde commented on BEAM-5954:
---------------------------------

Hey Robert, have you seen any failures like this recently? If not, please close this bug

> [Flake][Go PostCommit] Multiple Go Dataflow integration tests flaking.
> ----------------------------------------------------------------------
>
>                 Key: BEAM-5954
>                 URL: https://issues.apache.org/jira/browse/BEAM-5954
>             Project: Beam
>          Issue Type: Bug
>          Components: test-failures
>            Reporter: Daniel Oliveira
>            Assignee: Robert Burke
>            Priority: Minor
>
> In this run: [https://builds.apache.org/job/beam_PostCommit_Go_GradleBuild/1529/]
> The gradle build scan shows failures in tests cogbk:cogbk, wordcount:kinglear, pardo:multioutput, and flatten:flatten:
>  
> {noformat}
> 2018/11/02 06:07:15 Test cogbk:cogbk failed: job 2018-11-01_23_06_44-17028209533066002938 failed
> 2018/11/02 06:07:15 Job still running ...
> 2018/11/02 06:07:15 Test wordcount:kinglear failed: job 2018-11-01_23_06_44-16491289696282091455 failed
> 2018/11/02 06:07:15 Test pardo:multioutput failed: job 2018-11-01_23_06_44-9931794817698492697 failed
> 2018/11/02 06:07:15 Test flatten:flatten failed: job 2018-11-01_23_06_44-16704830194808169261 failed{noformat}
>  
>  
> In the following run: https://builds.apache.org/job/beam_PostCommit_Go_GradleBuild/1530/
> There's only a failure in test cogbk:cogbk:
>  
> {noformat}
> 2018/11/02 12:08:30 Test cogbk:cogbk failed: job 2018-11-02_05_07_59-8016502484320622028 failed{noformat}
>  
> Wasn't able to figure out how to investigate the individual tests' logs so I couldn't investigate what may be causing these failures.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)