GitHub user jameszhouyi opened a pull request:

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

    SPARK-3480 - Throws out Not a valid command 'yarn-alpha/scalastyle' in 
dev/scalastyle for sbt build tool during 'Running Scala style checks'

    Symptom:
    Run ./dev/run-tests and dump outputs as following:
    ....
    Running Scala style checks
    Scalastyle checks failed at following occurrences:
    [error] Expected ID character
    [error] Not a valid command: yarn-alpha
    [error] Expected project ID
    [error] Expected configuration
    [error] Expected ':' (if selecting a configuration)
    [error] Expected key
    [error] Not a valid key: yarn-alpha
    [error] yarn-alpha/scalastyle
    [error] ^
    
    Possible Cause:
    I checked the dev/scalastyle, found that there are 2 parameters 
'yarn-alpha/scalastyle' and 'yarn/scalastyle' separately,like
    echo -e "q\n" | sbt/sbt -Pyarn -Phadoop-0.23 -Dhadoop.version=0.23.9 
yarn-alpha/scalastyle \
    >> scalastyle.txt
    
    echo -e "q\n" | sbt/sbt -Pyarn -Phadoop-2.2 -Dhadoop.version=2.2.0 
yarn/scalastyle \
    >> scalastyle.txt
    
    From above error message, sbt seems to complain them due to '/' separator. 
So it can be run through after I manually modified original ones to 
'yarn-alpha:scalastyle' and 'yarn:scalastyle'..


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

    $ git pull https://github.com/jameszhouyi/spark branch-1.1

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

    https://github.com/apache/spark/pull/2359.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 #2359
    
----
commit c7d41ec666cf68f44cf362a3c05ac4d4dc9e74ab
Author: jameszhouyi <[email protected]>
Date:   2014-09-11T07:40:17Z

    SPARK-3480 - Throws out Not a valid command 'yarn-alpha/scalastyle' in 
dev/scalastyle for sbt build tool during 'Running Scala style checks'

----


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