[
https://issues.apache.org/jira/browse/SPARK-18878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15769663#comment-15769663
]
Sean Owen commented on SPARK-18878:
-----------------------------------
I understand why you need to fix some of these things in batches, but I see
https://issues.apache.org/jira/browse/SPARK-17591 and
https://issues.apache.org/jira/browse/SPARK-18785 with virtually the same
title. This has two child JIRAs that are also pretty much identical. This is no
longer very meaningful. Let's close down all but one JIRA for resource-closing
problems, and not resolve it until you're pretty sure they're done. Let's also
close general "umbrella" JIRAs like this. If there is a new type of Windows
problem, there can be a new JIRA targeted at that new type of fix, and again we
can make many PRs for one JIRA if needed to fix all of it in batches.
> Fix/investigate the more identified test failures in Java/Scala on Windows
> --------------------------------------------------------------------------
>
> Key: SPARK-18878
> URL: https://issues.apache.org/jira/browse/SPARK-18878
> Project: Spark
> Issue Type: Test
> Components: Tests
> Reporter: Hyukjin Kwon
>
> It seems many tests are being failed on Windows. Some are only related with
> tests whereas others are related with the functionalities themselves which
> causes actual failures for some APIs on Windows.
> The tests were hanging due to some issues in SPARK-17591 and SPARK-18785 and
> now apparently we could proceed much further (apparently it seems we might
> reach the end).
> The tests proceeded via AppVeyor -
> https://ci.appveyor.com/project/spark-test/spark/build/259-spark-test-windows
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
