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

Beam JIRA Bot commented on BEAM-14216:
--------------------------------------

This issue is assigned but has not received an update in 30 days so it has been 
labeled "stale-assigned". If you are still working on the issue, please give an 
update and remove the label. If you are no longer working on the issue, please 
unassign so someone else may work on it. In 7 days the issue will be 
automatically unassigned.

> Multiple XVR Suites having similar flakes simultaneously
> --------------------------------------------------------
>
>                 Key: BEAM-14216
>                 URL: https://issues.apache.org/jira/browse/BEAM-14216
>             Project: Beam
>          Issue Type: Bug
>          Components: cross-language, test-failures
>            Reporter: Daniel Oliveira
>            Assignee: Heejong Lee
>            Priority: P2
>              Labels: flake, stale-assigned
>
> Didn't have time to look very closely into the root cause, but in taking a 
> look at flaky cross-language tests I noticed a pattern of different suites on 
> different runners flaking at the same time. The specific ones that I've 
> noticed so far are:
> Samza: https://ci-beam.apache.org/job/beam_PostCommit_XVR_Samza/
> Spark: https://ci-beam.apache.org/job/beam_PostCommit_XVR_Spark/
> Dataflow: 
> https://ci-beam.apache.org/job/beam_PostCommit_XVR_PythonUsingJava_Dataflow/
> Example flake (Mar 29, 12 PM):
> https://ci-beam.apache.org/job/beam_PostCommit_XVR_Samza/993/
> https://ci-beam.apache.org/job/beam_PostCommit_XVR_Spark/3530/
> https://ci-beam.apache.org/job/beam_PostCommit_XVR_PythonUsingJava_Dataflow/242/
> Example flake 2 (Mar 30, 6 PM):
> https://ci-beam.apache.org/job/beam_PostCommit_XVR_Samza/998/
> https://ci-beam.apache.org/job/beam_PostCommit_XVR_Spark/3535/
> https://ci-beam.apache.org/job/beam_PostCommit_XVR_PythonUsingJava_Dataflow/247/



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Reply via email to