It appears that there is no one working on a fix for the flakes, so I've merged the change to disable parallel tasks on precommit.
Andrew On Fri, Aug 24, 2018 at 1:30 PM Andrew Pilloud <[email protected]> wrote: > I'm seeing failures due to this on 12 of the last 16 PostCommits. > Precommits take about 22 minutes run in parallel, so at a 25% pass rate > that puts the expected time to a good test run at 264 minutes assuming you > immediately restart on each failure. We are looking at 56 minutes for a > precommit that isn't run in parallel: > https://builds.apache.org/job/beam_PreCommit_Java_Phrase/266/ I'd rather > have tests take a little longer then have to monitor them for several hours. > > I've opened a PR: https://github.com/apache/beam/pull/6274 > > Andrew > > On Fri, Aug 24, 2018 at 10:47 AM Lukasz Cwik <[email protected]> wrote: > >> I believe it would mitigate the issue but also make the jobs take much >> longer to complete. >> >> On Thu, Aug 23, 2018 at 2:44 PM Andrew Pilloud <[email protected]> >> wrote: >> >>> There seems to be a misconfiguration of gradle that is causing a high >>> rate of failure for the last several weeks in building beam-examples-java >>> and beam-runners-apex. It appears to be some sort of race condition in >>> building dependencies. Given that no one has made progress on fixing the >>> root cause, is this something we could mitigate by running jobs with >>> `--no-parallel` flag? >>> >>> https://issues.apache.org/jira/browse/BEAM-5035 >>> https://issues.apache.org/jira/browse/BEAM-5207 >>> >>> Andrew >>> >>
