-
Notifications
You must be signed in to change notification settings - Fork 28.5k
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
SPARK-2482: Resolve sbt warnings during build #1330
Conversation
Merged build triggered. |
Merged build started. |
LGTM if tests pass. |
Were all of those imports being removed not required after all to avoid warnings? as long as that's the case (i.e. no build warnings) yes this is great IMHO. |
Merged build finished. All automated tests passed. |
All automated tests passed. |
Jenkins, retest this pleae. |
Jenkins, retest this please. |
QA tests have started for PR 1330. This patch merges cleanly. |
Could you paste exactly which warnings you are eliminating? I don't see any warnings in our master jenkins build that seem relevant to these changes. |
As a result of #772. The master has fixed this problem. But we should remove this line |
QA tests have started for PR 1330. This patch merges cleanly. |
QA results for PR 1330: |
QA tests have started for PR 1330. This patch merges cleanly. |
QA results for PR 1330: |
test this please |
This is a sort of duplicate of #1069 @witgo this was opened a few times? From the discussion, I am not clear this should be committed. The preferred practice here seems to be to In fact the compiler flag |
@andrewor14 , @srowen |
QA tests have started for PR 1330 at commit
|
QA tests have finished for PR 1330 at commit
|
@witgo Hi, I was asked to take a look at this PR. I tested the current master vs. this PR merged with the master, and I actually found that this PR added postfix warnings for me. (No postfix warnings in the master, but several with this PR.) Could you please show the warnings you get, plus info on what might be causing those warnings on your system? Thanks! |
15d5ed3
to
179ba61
Compare
The code has been updated. |
@@ -839,7 +839,6 @@ | |||
<arg>-unchecked</arg> | |||
<arg>-deprecation</arg> | |||
<arg>-feature</arg> | |||
<arg>-language:postfixOps</arg> |
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.
@jkbradley I removed this parameter. The related discussion in #1069
QA tests have started for PR 1330 at commit
|
QA tests have finished for PR 1330 at commit
|
The net-net change for all of these overlapping PRs should be: remove the compiler flag, and, add the import everywhere that the warning occurs. If there are warnings after this PR, they need to be squashed with more imports. |
No postfix warnings in 179ba61 . |
@witgo Sorry, I had not realized that this had not been updated since the discussions. Just tested it, and it worked for me. LGTM |
Ok, I am merging this over the alternative PR #1323, which is now closed. Thanks to everyone who looked at this. |
At the same time, import the
scala.language.postfixOps
andorg.scalatest.time.SpanSugar._
causescala.language.postfixOps
doesn't work