GitHub user nchammas opened a pull request:

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

    [Spark QA] only check code files for new classes

    Look only at code files (`.py`, `.java`, and `.scala`) for new classes.
    
    Should get rid of false alarms like [the one reported 
here](https://github.com/apache/spark/pull/2014#issuecomment-52912040).

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

    $ git pull https://github.com/nchammas/spark jenkins-ignore-noncode

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

    https://github.com/apache/spark/pull/2184.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 #2184
    
----
commit 3b26c8d4df4f106679f6724ae5aa1eb8f7582d90
Author: nchammas <[email protected]>
Date:   2014-08-26T18:22:55Z

    [Spark QA] Link to console output on test time out
    
    When tests time out we should link to the Jenkins console output for easy 
review. We already do this for when tests start or complete normally.
    
    Here's [a recent 
example](https://github.com/apache/spark/pull/2109#issuecomment-53374032) of 
where this would be helpful.

commit 9e2c72115ceabf74e5e1632ac87d3b6c3e612438
Author: Nicholas Chammas <[email protected]>
Date:   2014-08-28T21:18:29Z

    [Spark QA] only check code files for new classes
    
    Look only at code files (py, java, and scala) for new classes.
    
    Should get rid of false alarms like [the one reported
    here](https://github.com/apache/spark/pull/2014#issuecomment-52912040).

----


---
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