spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Cheung (JIRA)" <>
Subject [jira] [Commented] (SPARK-21693) AppVeyor tests reach the time limit, 1.5 hours, sometimes in SparkR tests
Date Thu, 10 Aug 2017 16:25:00 GMT


Felix Cheung commented on SPARK-21693:

we could certainly simplify the classification set - but there's a fair number of API being
tested in their, perhaps we could time them to see which ones are taking time.

> AppVeyor tests reach the time limit, 1.5 hours, sometimes in SparkR tests
> -------------------------------------------------------------------------
>                 Key: SPARK-21693
>                 URL:
>             Project: Spark
>          Issue Type: Test
>          Components: Build, SparkR
>    Affects Versions: 2.3.0
>            Reporter: Hyukjin Kwon
> We finally sometimes reach the time limit, 1.5 hours,
> I requested to increase this from an hour to 1.5 hours before but it looks we should
fix this in AppVeyor. I asked this for my account few times before but it looks we can't increase
this time limit again and again.
> I could identify two things that look taking a quite a bit of time:
> 1. Disabled cache feature in pull request builder, which ends up downloading Maven dependencies
(10-20ish mins)
> {quote}
> Note: Saving cache is disabled in Pull Request builds.
> {quote}
> and also see
> This seems difficult to fix within Spark.
> 2. "MLlib classification algorithms" tests (30-35ish mins)
> This test below looks taking 30-35ish mins.
> {code}
> MLlib classification algorithms, except for tree-based algorithms: Spark package found
in SPARK_HOME: C:\projects\spark\bin\..
> ......................................................................
> {code}
> As a (I think) last resort, we could make a matrix for this test alone, so that we run
the other tests after a build and then run this test after another build, for example, I run
Scala tests by this workaround -
(a matrix with 7 build and test each).
> I am also checking and testing other ways.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message