[
https://issues.apache.org/jira/browse/BEAM-13693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17495181#comment-17495181
]
Beam JIRA Bot commented on BEAM-13693:
--------------------------------------
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.
> beam_PostCommit_Java_ValidatesRunner_Dataflow_Streaming timing out at 9 hours
> -----------------------------------------------------------------------------
>
> Key: BEAM-13693
> URL: https://issues.apache.org/jira/browse/BEAM-13693
> Project: Beam
> Issue Type: Bug
> Components: runner-dataflow, test-failures
> Reporter: Brian Hulette
> Assignee: Kenneth Knowles
> Priority: P1
> Labels: currently-failing, stale-assigned
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> This suite started timing out at
> https://ci-beam.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Dataflow_Streaming/1790/
> That build includes the bom update which seems like a likely culprit, but
> note that previous non-cached runs were taking 8h55m (e.g.
> https://ci-beam.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Dataflow_Streaming/1784/),
> so we were already cutting it close.
> [~kenn] do you want to just bump up the timeout further?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
