-
Notifications
You must be signed in to change notification settings - Fork 28.9k
[WIP][SPARK-18896][TESTS] Update to ScalaTest 3.0.1 #16309
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
pom.xml
Outdated
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.
Hi @jaceklaskowski, I just wonder if it is safe assuming from the comment beside, 1.13.0 appears incompatible with scalatest 2.2.6. I just read https://github.com/rickynils/scalacheck/issues/217 BTW.
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.
Thanks. The local build has passed so I'm now waiting for Jenkins to say how it liked the change (or not).
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.
Yes, I remember this didn't work. Jenkins runs SBT; are you checking Maven locally?
I'd like to update, sure, but want to make sure we don't trip over whatever I found before.
We could consider updating to scalatest 3.0.1 as well, in any event. As a test-only dependency it should be safe to more freely update it.
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.
Yes, I did use maven for the entire local built and sbt for this particular DAGSchedulerSuite (that it all started from actually).
I've got little experience with Spark test suite and hence I'm relying on Jenkins to do the heavy-lifting and see how things may have changed since the comment.
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.
sbt.ForkMain$ForkError: sbt.ForkMain$ForkError: java.lang.IncompatibleClassChangeError: Implementing class
You were both indeed right. Let me dig into it a bit more...
|
Test build #70243 has finished for PR 16309 at commit
|
|
Yup, doesn't work I'm afraid: Does 1.12.6 fix it? otherwise, I wonder what upgrading scalatest does? |
|
Right. Testing ScalaTest 3.0.1 with the following sbt command: Is this correct to be as close to Jenkins as possible? |
|
Had to introduce changes to the tests given "Expired deprecations" in ScalaTest 3.0.0. |
|
Test build #70249 has finished for PR 16309 at commit
|
|
Just learnt about |
|
Learnt about |
|
Test build #70250 has finished for PR 16309 at commit
|
|
Test build #70251 has finished for PR 16309 at commit
|
|
Think the latest test failures are somehow related to:
BTW, I'm using |
|
Hey @srowen, any idea about the following error? I'd appreciate any hints to help me fix it. and |
|
That's a simple "out of memory". Did you give SBT 4-6GB? |
|
I'm testing the changes locally with the following: It's been running for the past one hour and looks fine so far. I faced some SQL UDF-related errors that didn't look like mine so had to re-test everything again. I however got no changes to push so...how can I re-trigger tests on Jenkins to see if it's something temporary? Is there some magic Jenkins trigger? |
|
2G is not enough. I use 4G at least. |
0484efd to
b3c8f48
Compare
|
Rebasing with master to trigger tests on Jenkins...(hoping this time they pass) |
|
Test build #70306 has finished for PR 16309 at commit
|
|
@srowen Please help as I'm stuck with the What's even more interesting is that the tests seem to have all passed according to the report in Test build #70306 has finished. BTW, I'm running the tests on my laptop with the following settings |
|
The tests ran locally on my laptop have finished after... Not sure why I'm getting |
|
Test build #3509 has finished for PR 16309 at commit
|
|
You probably have a typo -- The only interesting thing I spy is that one of the traces involves scala XML code, and you updated to If it's resolvable, let's try to update to scalatest 3. if not, see if plugin 1.12.6 fixes the minor warning. If not, I'd punt on this for now. You could leave the JIRA open as "update to scalatest 3" for a later look then. |
|
The reason for the update to You may be right that updating the jar could have impacted the XML issue Jenkins's reporting. Let me see if I can somehow relate them by:
Thanks for the hint! |
|
In order to finish this thought, let's either update scalatest to just 1.12.6 if that solves it, or do nothing. In the latter case, you could leave the JIRA open as an 'update to scalatest 3' JIRA for later, though I don't know how to track down why it fails. |
|
The changes between scala-xml 1.0.2 and 1.0.5 are in this view. For reference: scala-xml releases |
b3c8f48 to
d57f03c
Compare
|
Test build #70598 has finished for PR 16309 at commit
|
Closes apache#15736 Closes apache#16309 Closes apache#16485 Closes apache#16502 Closes apache#16196 Closes apache#16498 Closes apache#12380 Closes apache#16764
What changes were proposed in this pull request?
Fixes ScalaCheck warning by upgrading to the latest 1.13.4 version.
The reason is due to a bug in ScalaCheck as reported in typelevel/scalacheck#212 and fixed in typelevel/scalacheck@df435a5 that is available in ScalaCheck 1.13.4.
Spark uses ScalaCheck 1.12.5 which is behind the latest 1.12.6 released on Nov 1 (not to mention 1.13.4).
How was this patch tested?
Local build. Waiting for Jenkins.