[
https://issues.apache.org/jira/browse/BEAM-13693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17499156#comment-17499156
]
Brian Hulette commented on BEAM-13693:
--------------------------------------
Runtime down to ~6h30m in
https://ci-beam.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Dataflow_Streaming/1910/,
I think we can close this now.
> 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
> Priority: P1
> Labels: currently-failing
> 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)
