You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Josh Rosen (JIRA)" <ji...@apache.org> on 2015/06/17 21:19:00 UTC
[jira] [Resolved] (SPARK-7020) Restrict module testing based on
commit contents
[ https://issues.apache.org/jira/browse/SPARK-7020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Rosen resolved SPARK-7020.
-------------------------------
Resolution: Fixed
Fix Version/s: 1.5.0
Assignee: Brennon York
I'm going to resolve this as fixed by SPARK-7017, since that PR adds basic support for this.
> Restrict module testing based on commit contents
> ------------------------------------------------
>
> Key: SPARK-7020
> URL: https://issues.apache.org/jira/browse/SPARK-7020
> Project: Spark
> Issue Type: Improvement
> Components: Build, Project Infra
> Reporter: Brennon York
> Assignee: Brennon York
> Priority: Critical
> Fix For: 1.5.0
>
>
> Currently all builds trigger all tests. This does not need to happen and, to minimize the test window, the {{git}} commit contents should be checked to determine which modules were affected and, for each, only run those tests.
--
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