[jira] [Updated] (SPARK-10300) Use tags to control which tests to run depending on changes being tested

["Marcelo Vanzin (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SPARK-10300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcelo Vanzin updated SPARK-10300:
-----------------------------------
         Assignee: Marcelo Vanzin
    Fix Version/s: 1.6.0
       Issue Type: Improvement  (was: Bug)

> Use tags to control which tests to run depending on changes being tested
> ------------------------------------------------------------------------
>
>                 Key: SPARK-10300
>                 URL: https://issues.apache.org/jira/browse/SPARK-10300
>             Project: Spark
>          Issue Type: Improvement
>          Components: Build, Tests
>            Reporter: Marcelo Vanzin
>            Assignee: Marcelo Vanzin
>            Priority: Minor
>             Fix For: 1.6.0
>
>
> Our unit tests are a little slow, and we could benefit from finer-grained control over which test suites to run depending on what parts of the code base is changed.
> Currently we already have some logic in "run-tests.py" to do this, but it's limited; for example, a minor change in an untracked module is mapped to a "root" module change, and causes really expensive Hive compatibility tests to run when that may not really be necessary.
> Using tags could allow us to be smarter here; this is an idea that has been thrown around before (e.g. SPARK-4746). On top of that, for the cases when we actually do need to run all the tests, we should bump the existing timeout.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org