the timer is set to 500m now in master, 3.0 and 2.4. On Thu, May 28, 2020 at 12:32 PM Kousuke Saruta <saru...@oss.nttdata.com> wrote:
> Thanks all. It's very helpful! > > - Kousuke > > On 2020/05/29 3:31, shane knapp ☠ wrote: > > https://github.com/apache/spark/pull/28666 > > On Thu, May 28, 2020 at 11:20 AM shane knapp ☠ <skn...@berkeley.edu> > wrote: > >> i'll get a PR put together now. >> >> On Thu, May 28, 2020 at 8:26 AM Hyukjin Kwon <gurwls...@gmail.com> wrote: >> >>> I remember we were able to cut down pretty considerably in the past. For >>> example, I investigated ( >>> https://github.com/apache/spark/pull/21822#issuecomment-407295739) >>> and fixed some before at, like >>> https://github.com/apache/spark/pull/23111. Maybe we could skim again >>> to reduce the build/testing time .. >>> >>> But I agree with increasing it at this moment for now to unblock PRs. >>> Don't forget to fix here too >>> https://github.com/apache/spark/blob/master/dev/run-tests-jenkins.py#L201 >>> :-). >>> >>> 2020년 5월 29일 (금) 오전 12:14, shane knapp ☠ <skn...@berkeley.edu>님이 작성: >>> >>>> On Thu, May 28, 2020 at 7:16 AM Sean Owen <sro...@gmail.com> wrote: >>>> >>>>> What else can we do, I suppose? >>>>> >>>>> there,s not much else we can do. i'll add 30m to the timeout. >>>> >>>> shane >>>> -- >>>> Shane Knapp >>>> Computer Guy / Voice of Reason >>>> UC Berkeley EECS Research / RISELab Staff Technical Lead >>>> https://rise.cs.berkeley.edu >>>> >>> >> >> -- >> Shane Knapp >> Computer Guy / Voice of Reason >> UC Berkeley EECS Research / RISELab Staff Technical Lead >> https://rise.cs.berkeley.edu >> > > > -- > Shane Knapp > Computer Guy / Voice of Reason > UC Berkeley EECS Research / RISELab Staff Technical Lead > https://rise.cs.berkeley.edu > > > -- Shane Knapp Computer Guy / Voice of Reason UC Berkeley EECS Research / RISELab Staff Technical Lead https://rise.cs.berkeley.edu
