It may also be advantageous to separate most submodules to not run a giant generic Java precommit. Each IO really only needs its own, and to register itself in the global Java precommit run only for the core. The bookkeeping may become quite a lot, but this is the natural structure.
Kenn On Mon, Oct 28, 2019 at 6:12 PM Chad Dombrova <chad...@gmail.com> wrote: > Can we get more aggressive about separating tests into groups by those > that are dependent on other languages and those that are not? I think we > could dramatically reduce our backlog if we didn’t run all of the Java > tests every time a commit is made that only affects python code, and vice > versa. > > -chad > > > On Mon, Oct 28, 2019 at 3:05 PM Mikhail Gryzykhin <mig...@google.com> > wrote: > >> Quota jira issue: >> https://issues.apache.org/jira/browse/BEAM-8195 >> >> On Mon, Oct 28, 2019 at 2:05 PM Mikhail Gryzykhin <mig...@google.com> >> wrote: >> >>> Hi everyone, >>> >>> >>> While validating release branch, I got failure due Quota again. Also, >>> current queue time for jobs is more than 1.5 hours. >>> >>> >>> I'm not sure if it is worth starting another thread on tests efficiency, >>> but still want to keep this mail to highlight the issues. >>> >>> >>> See PS for links. >>> >>> >>> Regards, >>> >>> --Mikhail >>> >>> >>> PS: >>> >>> https://builds.apache.org/job/beam_PostCommit_Go_PR/71/consoleFull >>> >>> *13:46:25* 2019/10/28 20:46:25 Test wordcount:kinglear failed: googleapi: >>> Error 429: Quota exceeded for quota metric >>> 'dataflow.googleapis.com/create_requests' and limit >>> 'CreateRequestsPerMinutePerUser' of service 'dataflow.googleapis.com' for >>> consumer 'project_number:844138762903'., rateLimitExceeded >>> >>> >>> Queue time: >>> >>> http://metrics.beam.apache.org/d/_TNndF2iz/pre-commit-test-latency?orgId=1 >>> >>>
