update: we're seeing about 3% of builds timing out, but today is (so far) a bad one:
i've reached out to github about this and am waiting to hear back. $ get_timeouts.py 10 Timeouts by project: 17 spark-branch-2.3-lint 10 spark-branch-2.3-test-maven-hadoop-2.6 7 spark-branch-2.3-compile-maven-hadoop-2.7 41 spark-master-lint 23 spark-master-compile-maven-hadoop-2.6 32 spark-master-compile-maven-hadoop-2.7 5 spark-branch-2.2-compile-maven-hadoop-2.6 3 spark-branch-2.2-test-maven-hadoop-2.7 6 spark-branch-2.2-compile-maven-scala-2.10 6 spark-master-test-maven-hadoop-2.6 3 spark-master-test-maven-hadoop-2.7 14 spark-branch-2.3-compile-maven-hadoop-2.6 3 spark-branch-2.2-lint 1 spark-branch-2.3-test-maven-hadoop-2.7 Timeouts by day: 2018-01-09 4 2018-01-10 13 2018-01-11 27 2018-01-12 74 2018-01-13 9 2018-01-14 2 2018-01-15 8 2018-01-16 34 Total builds: 4112 Total timeouts: 171 Percentage of all builds timing out: 4.15856031128 On Wed, Jan 10, 2018 at 9:54 AM, shane knapp <skn...@berkeley.edu> wrote: > i just noticed we're starting to see the once-yearly rash of git timeouts > when building. > > i'll be looking in to this today... i'm at our lab retreat, so my > attention will be divided during the day but i will report back here once i > have some more information. > > in the meantime, if your jobs have a git timeout, please just retrigger > them and we will hope for the best. > > shane >
