Hi, All and Shane.
Can we increase the build time for `branch-2.3` during 2.3 RC period?
There are two known test issues, but the Jenkins on branch-2.3 with hadoop-2.7 fails with build timeout. So, it's difficult to monitor whether the branch is healthy or not.
Build timed out (after 255 minutes). Marking the build as aborted.
Build was aborted
seems like someone should investigate what caused the build time to go up an hour and if it's expected or not.
On Thu, Jan 11, 2018 at 7:37 PM, Dongjoon Hyun <[hidden email]> wrote:
FYI, we reverted a commit in https://github.com/apache/spark/commit/55dbfbca37ce4c05f83180777ba3d4fe2d96a02e to fix the issue.
On Fri, Jan 12, 2018 at 11:45 AM, Xin Lu <[hidden email]> wrote:
2. Marco Gaido reports a flaky test suite and it turns out that the test suite hangs in SPARK-23055
For this issue, during SPARK-23028, Shane shared that the server limit is already higher.
1. Xiao Li increased the timeout of Spark test script for `master` branch first in the following commit.[SPARK-23028] Bump master branch version to 2.4.0-SNAPSHOT
3. Sameer Agarwal swiftly reverts it.
Thank you all!
On Fri, Jan 12, 2018 at 3:22 PM, Shixiong(Ryan) Zhu <[hidden email]> wrote:
FYI, I ended up bumping the build timeouts from 255 to 275 minutes. All successful 2.3 (hadoop-2.7) builds last week were already taking 245-250 mins and had started timing out earlier today (towards the very end; while making consistent progress throughout). Increasing the timeout resolves the issue.
NB: This might be either due to additional tests that were recently added or due to the git delays that Shane reported; we haven't investigated the root cause yet.
On 12 January 2018 at 16:37, Dongjoon Hyun <[hidden email]> wrote:
this doesn't have anything to do w/the git timeouts... those will timeout the build 10 mins after starting (and failing on the initial fetch call).
On Wed, Jan 17, 2018 at 9:51 PM, Sameer Agarwal <[hidden email]> wrote:
|Free forum by Nabble||Edit this page|