-
Notifications
You must be signed in to change notification settings - Fork 28.9k
[SPARK-23028] Bump master branch version to 2.4.0-SNAPSHOT #20222
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Yeah ideally that's part of the branching process. I think it could be documented in the "Preparing Spark for Release" section of |
|
@srowen Yeah. I am still in travel mode. : ) Please help do it. Thanks! |
|
@JoshRosen or @shaneknapp looks like we also need to have set up the branch-2.3 tests in Jenkins. Right now it's not tested. I might have access to do it. Is it safe to copy and paste existing jobs and change the branch reference? |
|
We should already be set up for 2.3.x builds in AMPLab Jenkins. For example: https://amplab.cs.berkeley.edu/jenkins/view/Spark%20QA%20Test/job/spark-branch-2.3-test-maven-hadoop-2.6/ |
| */ | ||
| object MimaExcludes { | ||
|
|
||
| // Exclude rules for 2.4.x |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This reminds me that we should probably bump previousSparkVersion in MimaBuild.scala to be 2.2.0: https://github.com/apache/spark/blame/f340b6b3066033d40b7e163fd5fb68e9820adfb1/project/MimaBuild.scala#L91. I think this should happen for both master and branch-2.3.
See #15061 for an example of a similar change when 2.1.x was being prepared (it looks like we missed this step for 2.2.0). We may also need to un-exclude any new subprojects / artifacts that were added in 2.2.0 since they now need to be backwards-compatibility-tested for 2.3.x.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We might want to make my proposed MiMa changes in a separate patch so the same set of reviewed changes can go to both master and branch-2.3.
|
Oh I see, they're just not listed on https://amplab.cs.berkeley.edu/jenkins/view/Spark%20QA%20Test%20(Dashboard)/ . I believe I can fix that. |
|
Wait
dev/create-release/release-tag.sh does this automatically though.
I just want to make sure we are not missing things (like R/pkg/DESCRIPTION)
I think maybe we should run a subset of release-tag
|
|
Test build #85922 has finished for PR 20222 at commit
|
|
Test build #85923 has finished for PR 20222 at commit
|
|
argh. i'll bump the job timeout now.
…On Wed, Jan 10, 2018 at 12:19 PM, UCB AMPLab ***@***.***> wrote:
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/85923/
Test FAILed.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#20222 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABiDrAOQSJRXi3DeWcIaxSmSuX7ayuawks5tJRtYgaJpZM4RZdH7>
.
|
|
retest this please |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we update python/pyspark/version.py too?
|
Test build #85935 has finished for PR 20222 at commit
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
by looking at release-tag,
python/pyspark/version.py is another one we need to update, note it should say 2.4.0.dev0
https://github.com/apache/spark/blob/master/dev/create-release/release-tag.sh#L87
|
Thanks for your review! |
|
Test build #85952 has finished for PR 20222 at commit
|
|
Jenkins, retest this please. |
|
Test build #85955 has finished for PR 20222 at commit
|
|
@shaneknapp Could we bump the job timeout? |
|
retest this please |
|
@gatorsmile -- the timeout is currently at six hours. i am loathe to bump it any higher. |
|
Test build #85966 has finished for PR 20222 at commit
|
|
test this please |
|
Test build #85980 has finished for PR 20222 at commit
|
|
retest this please |
|
I think we should fix: spark/dev/run-tests-jenkins.py Lines 183 to 185 in 7c7bc8f
too. cc @JoshRosen, since you increased time before IIRC. |
|
Test build #85996 has finished for PR 20222 at commit
|
| # must be less than the timeout configured on Jenkins (currently 300m) | ||
| tests_timeout = "250m" | ||
| # must be less than the timeout configured on Jenkins (currently 350m) | ||
| tests_timeout = "300m" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, this was the root causes. Thanks, @HyukjinKwon .
Sorry, @shaneknapp . I sent an annoying email before knowing this here.
|
Test build #86008 has finished for PR 20222 at commit
|
|
retest this please |
|
Test build #86021 has finished for PR 20222 at commit
|
|
retest this please |
|
BTW, does anyone know why it suddently takes logner time? |
| # format: http://linux.die.net/man/1/timeout | ||
| # must be less than the timeout configured on Jenkins (currently 300m) | ||
| tests_timeout = "250m" | ||
| # must be less than the timeout configured on Jenkins (currently 350m) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not a big deal but seems currently we set it to 361m in Jenkins now - cc @shaneknapp.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this comment is OK.
|
Test build #86026 has finished for PR 20222 at commit
|
|
Unlike the other PRs, this PR changes all the POMs. It requires running all the test cases. Thus, this hit the limit. |
|
No, all the others seems to suffer together. |
|
is it good to go? |
|
LGTM, merging to master! |
|
BTW don't forget #20222 (comment) :) |

What changes were proposed in this pull request?
This patch bumps the master branch version to
2.4.0-SNAPSHOT.How was this patch tested?
N/A