Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/12980#issuecomment-217805705
I don't think it's a bad thing to have some kind of Travis build running in
parallel as long as people understand what it is. Maybe some extra comments in
the .travis.yml file to explain its purpose?
So it sounds like we could actually re-enable lint in the main build, but
the concern is speed? but the Java lint checks themselves seem to take just a
few seconds:
```
$ time ./dev/lint-java
Using `mvn` from path: /usr/local/bin/mvn
Checkstyle checks passed.
real 0m7.949s
user 0m26.882s
sys 0m1.144s
```
Almost all the time in that Travis run is downloading stuff, compiling, and
running the other lint 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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
