[
https://issues.apache.org/jira/browse/BEAM-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15900734#comment-15900734
]
Kenneth Knowles commented on BEAM-1647:
---------------------------------------
But other obvious places that, given adequate configurability, we should be
able to save:
- 5 minutes of downloading at the start; maybe more later?
- I definitely see two occurrences of ParDoTest, which is suspicious. If we
are redundantly running unit tests of prerequisites, as is usual for Maven,
adding "skip" configs there could save 3-5 minutes.
> Dataflow RunnableOnService tests timing out reliably
> ----------------------------------------------------
>
> Key: BEAM-1647
> URL: https://issues.apache.org/jira/browse/BEAM-1647
> Project: Beam
> Issue Type: Bug
> Components: runner-dataflow, testing
> Reporter: Kenneth Knowles
> Assignee: Davor Bonaci
> Priority: Blocker
>
> Since [build
> 2487|https://builds.apache.org/view/Beam/job/beam_PostCommit_Java_RunnableOnService_Dataflow/2487/]
> our build time seems to have pushed up past 1h40m and is timing out.
> It was just barely under that anyhow, so I don't expect this is a
> catastrophic change but probably something small. Some builds (at HEAD) seem
> to sneak under the limit.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
