Not sure where other perf issues are coming from, but this specific BQ test suite was disabled yesterday: https://github.com/apache/beam/pull/6658
On Fri, Oct 12, 2018 at 3:20 PM Kenneth Knowles <[email protected]> wrote: > Nice catch. Here is a build that went from 2.5 to 3 hours: > https://builds.apache.org/view/A-D/view/Beam/job/beam_PostCommit_Java_GradleBuild/1654/ > looks like it added some BQ tests. Not sure that can account for it. > > From there it was red for some time and slow once it went green again and > was already slowed. > > I'd suggest that postcommit Dataflow integration tests have their own > build that does not run anything else. That's something you can do now that > we use Gradle that was not possible with mvn (except via Jenkins shell job). > > Kenn > > On Fri, Oct 12, 2018 at 11:33 AM Mikhail Gryzykhin <[email protected]> > wrote: > >> Hi everyone, >> >> I just wanted to highlight an interesting fact: Our java postcommits >> duration almost *doubled* since last week rising from 2.2 to nearly 4 >> hours. (See bottom-left graph on this dashboard >> <http://104.154.241.245/d/D81lW0pmk/post-commit-tests?orgId=1>) >> >> We might want to check on the tests we are adding lately. >> >> Regards, >> --Mikhail >> >> Have feedback <http://go/migryz-feedback>? >> >
