It looks like beam_PostCommit_Py_VR_Dataflow has been timing out at 1h40m
since Dec 4 [1]. Are there any objections to bumping up the timeout to
alleviate this? Or any other thoughts on potential causes and/or solutions?

Brian

[1] https://builds.apache.org/job/beam_PostCommit_Py_VR_Dataflow/

Reply via email to