Skip to content

Conversation

@gatorsmile
Copy link
Member

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

@gatorsmile
Copy link
Member Author

gatorsmile commented Jan 10, 2018

@srowen
Copy link
Member

srowen commented Jan 10, 2018

Yeah ideally that's part of the branching process. I think it could be documented in the "Preparing Spark for Release" section of release-process.md in spark-website. Open up a separate PR for that if you like, or I can do it if you're not set up for it.

@gatorsmile
Copy link
Member Author

@srowen Yeah. I am still in travel mode. : ) Please help do it. Thanks!

@srowen
Copy link
Member

srowen commented Jan 10, 2018

R/pkg/DESCRIPTION needs an update too.
I'll update the release process.

@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?

@JoshRosen
Copy link
Contributor

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
Copy link
Contributor

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.

Copy link
Contributor

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.

@srowen
Copy link
Member

srowen commented Jan 10, 2018

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.

@felixcheung
Copy link
Member

felixcheung commented Jan 10, 2018 via email

@SparkQA
Copy link

SparkQA commented Jan 10, 2018

Test build #85922 has finished for PR 20222 at commit 3e1d6d6.

  • This patch fails SparkR unit tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@SparkQA
Copy link

SparkQA commented Jan 10, 2018

Test build #85923 has finished for PR 20222 at commit 9107f9f.

  • This patch fails from timeout after a configured wait of `250m`.
  • This patch merges cleanly.
  • This patch adds no public classes.

@shaneknapp
Copy link
Contributor

shaneknapp commented Jan 10, 2018 via email

@jiangxb1987
Copy link
Contributor

retest this please

Copy link
Member

@HyukjinKwon HyukjinKwon left a 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?

@SparkQA
Copy link

SparkQA commented Jan 11, 2018

Test build #85935 has finished for PR 20222 at commit 9107f9f.

  • This patch fails from timeout after a configured wait of `250m`.
  • This patch merges cleanly.
  • This patch adds no public classes.

Copy link
Member

@felixcheung felixcheung left a 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

@gatorsmile
Copy link
Member Author

Thanks for your review!

@SparkQA
Copy link

SparkQA commented Jan 11, 2018

Test build #85952 has finished for PR 20222 at commit 5eded03.

  • This patch fails due to an unknown error code, -9.
  • This patch merges cleanly.
  • This patch adds no public classes.

@ueshin
Copy link
Member

ueshin commented Jan 11, 2018

Jenkins, retest this please.

@SparkQA
Copy link

SparkQA commented Jan 11, 2018

Test build #85955 has finished for PR 20222 at commit 5eded03.

  • This patch fails from timeout after a configured wait of `250m`.
  • This patch merges cleanly.
  • This patch adds no public classes.

@gatorsmile
Copy link
Member Author

@shaneknapp Could we bump the job timeout?

@HyukjinKwon
Copy link
Member

retest this please

@shaneknapp
Copy link
Contributor

@gatorsmile -- the timeout is currently at six hours. i am loathe to bump it any higher.

@SparkQA
Copy link

SparkQA commented Jan 11, 2018

Test build #85966 has finished for PR 20222 at commit 5eded03.

  • This patch fails from timeout after a configured wait of `250m`.
  • This patch merges cleanly.
  • This patch adds no public classes.

@shaneknapp
Copy link
Contributor

confused:
screen shot 2018-01-11 at 9 39 00 am

anyways, i will change the timeout. again.

@shaneknapp
Copy link
Contributor

test this please

@SparkQA
Copy link

SparkQA commented Jan 11, 2018

Test build #85980 has finished for PR 20222 at commit 5eded03.

  • This patch fails from timeout after a configured wait of `250m`.
  • This patch merges cleanly.
  • This patch adds no public classes.

@jiangxb1987
Copy link
Contributor

retest this please

@HyukjinKwon
Copy link
Member

I think we should fix:

# format: http://linux.die.net/man/1/timeout
# must be less than the timeout configured on Jenkins (currently 300m)
tests_timeout = "250m"

too.

cc @JoshRosen, since you increased time before IIRC.

@SparkQA
Copy link

SparkQA commented Jan 12, 2018

Test build #85996 has finished for PR 20222 at commit 5eded03.

  • This patch fails from timeout after a configured wait of `250m`.
  • This patch merges cleanly.
  • This patch adds no public classes.

# 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"
Copy link
Member

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.

@SparkQA
Copy link

SparkQA commented Jan 12, 2018

Test build #86008 has finished for PR 20222 at commit 440d11f.

  • This patch fails Spark unit tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@HyukjinKwon
Copy link
Member

retest this please

@SparkQA
Copy link

SparkQA commented Jan 12, 2018

Test build #86021 has finished for PR 20222 at commit 440d11f.

  • This patch fails due to an unknown error code, -9.
  • This patch merges cleanly.
  • This patch adds no public classes.

@HyukjinKwon
Copy link
Member

retest this please

@HyukjinKwon
Copy link
Member

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)
Copy link
Member

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.

Copy link
Member Author

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.

@SparkQA
Copy link

SparkQA commented Jan 12, 2018

Test build #86026 has finished for PR 20222 at commit 440d11f.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@gatorsmile
Copy link
Member Author

Unlike the other PRs, this PR changes all the POMs. It requires running all the test cases. Thus, this hit the limit.

@dongjoon-hyun
Copy link
Member

No, all the others seems to suffer together.
I think this might be related to the intel patch done by Shane a few days ago.

@cloud-fan
Copy link
Contributor

is it good to go?

@cloud-fan
Copy link
Contributor

cloud-fan commented Jan 12, 2018

LGTM, merging to master!

@cloud-fan
Copy link
Contributor

BTW don't forget #20222 (comment) :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.