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

Daniel Oliveira commented on BEAM-6284:
---------------------------------------

This issue is being actively investigated internally in Dataflow right now, 
which is why there aren't any visible updates here. It seems valuable to keep 
this bug up and keep recording instances of this happening, so I'll try to keep 
this bug updated with progress so it doesn't look like it's being ignored.

> [FLAKE][beam_PostCommit_Java_ValidatesRunner_Dataflow] TestRunner fails with 
> result UNKNOWN on succeeded job and checks passed
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: BEAM-6284
>                 URL: https://issues.apache.org/jira/browse/BEAM-6284
>             Project: Beam
>          Issue Type: Bug
>          Components: test-failures, testing
>            Reporter: Mikhail Gryzykhin
>            Assignee: Daniel Oliveira
>            Priority: Major
>              Labels: currently-failing
>
> _Use this form to file an issue for test failure:_
>  * 
> https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Dataflow/lastCompletedBuild/testReport/junit/org.apache.beam.sdk.transforms/ViewTest/testWindowedSideInputFixedToGlobal/
> Initial investigation:
> According to logs all test-relevant checks have passed and it seem to be 
> testing framework failure.
> ----
> _After you've filled out the above details, please [assign the issue to an 
> individual|https://beam.apache.org/contribute/postcommits-guides/index.html#find_specialist].
>  Assignee should [treat test failures as 
> high-priority|https://beam.apache.org/contribute/postcommits-policies/#assigned-failing-test],
>  helping to fix the issue or find a more appropriate owner. See [Apache Beam 
> Post-Commit 
> Policies|https://beam.apache.org/contribute/postcommits-policies]._



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

Reply via email to