-
Notifications
You must be signed in to change notification settings - Fork 28.7k
Fix postfixOps warnings in the test suite #1323
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
This covers a lot of the same ground as #1153 . It would be great to get all of this in to stop the warnings. |
Merged build triggered. |
Merged build started. |
@srowen sorry, I hadn't noticed the other PR! I think the |
Merged build finished. All automated tests passed. |
All automated tests passed. |
I just merged #1153 and unfortunately this one is no longer mergeable. Will - mind updating it? |
Merged build triggered. |
Merged build started. |
Merged build finished. All automated tests passed. |
All automated tests passed. |
Previously, language.postfixOps was imported at toplevel, which meant compiler warnings since it wasn't visible inside the classes that used postfix operations. This commit moves the import to suppress these warnings.
QA tests have started for PR 1323. This patch merges cleanly. |
Related work #1330 |
QA results for PR 1323: |
Can someone take a look at this again? |
@willb Hi, I was asked to take a look at this. I tried the current master + this PR merged with master, and I did not see much difference in warnings (or any warnings about postfixOps). Could you please show the warnings, and info which might indicate the system/setup which produces the warnings? Thank you! |
Hi @jkbradley; thanks for taking a look. Here are the warnings as I see them when compiling tests on the immediate ancestor of my branch, which is 56e009d (I'm running on OS X 10.9 in this case):
Moving the import to within the test class (as in my patch) eliminated the warnings. |
Hey @andrewor14, thanks for the reply. First off, I absolutely agree with @srowen's comment on #1330 that In any case, the approach in #1330 is probably the way to go since explicitly importing |
I see, thanks for your patch anyway! |
…ault (apache#1323) ### What changes were proposed in this pull request? This PR aims to add a new executor roll policy, `OUTLIER`, which aims to detect various outliers first, and use it by default. If there is no outlier, it will work like `TOTAL_DURATION` policy. ### Why are the changes needed? The users can use `OUTLIER` policy to consider the outliers in terms of multiple dimensions. In addition, this will be a better default policy. ### Does this PR introduce _any_ user-facing change? No. This is a new feature in Apache Spark 3.3. ### How was this patch tested? Pass the CIs with the newly added test cases.
This PR fixes compiler warnings in the test suite related to
scala.language.postfixOps
not being in scope within the test classes in which postfix operations were actually used.