GitHub user vanzin opened a pull request:

    https://github.com/apache/spark/pull/8775

    [SPARK-10300] [BUILD] [TESTS] Add support for test tags in run-tests.py.

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/vanzin/spark SPARK-10300

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/8775.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #8775
    
----
commit abb07a126bf59cb3954f6b01b29f38d636d56e1f
Author: Marcelo Vanzin <[email protected]>
Date:   2015-09-15T20:05:23Z

    [SPARK-10300] [BUILD] [TESTS] Add support for test tags in run-tests.py.

commit 9e0b3c4fee3b88b012efc479d4831034e144e04b
Author: Marcelo Vanzin <[email protected]>
Date:   2015-09-15T22:21:33Z

    Move test tags to a separate module.
    
    A new module ("tags/") was added where all test tags should be placed.
    This is required because the JUnit runners for both maven and sbt require
    the classes to be visible when you disable them, even if no tests actually
    reference them.
    
    To avoid a cyclic dependency, the tags dependency needs to be manually added
    to all poms, which is annoying. An alternative would be to make the tag
    module's pom not have spark-parent as its parent, but that would mean
    replicating some information from the parent pom and fixing other code
    (such as the "change-scala-version.sh" script).

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to