[
https://issues.apache.org/jira/browse/SPARK-18878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15750709#comment-15750709
]
Hyukjin Kwon edited comment on SPARK-18878 at 12/15/16 8:02 AM:
----------------------------------------------------------------
cc [~srowen] Currently, the test failures were not able to be identified all
due to the time limitation (one hour) in AppVeyor. This was increased for my
account after manually asking - https://github.com/appveyor/ci/issues/517 up to
one hour and 30 minutes but it seems it can't be increased more than that.
I will specify the errors within the description in each child task after
manually testing separately when it is required.
was (Author: hyukjin.kwon):
cc [~srowen] Currently, the test failures were not able to be identified all
due to the time limitation (one hour) in AppVeyor. This was increased for my
account after manually asking - https://github.com/appveyor/ci/issues/517 but
it seems it can't be increased that much. (It is increased up to one hour and
30 minutes).
I will specify the errors within each child task after manually testing
separately when it is required.
> 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]
