Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14892
Looks like it's about 7 minutes 32 seconds out of 1 hour 49 minutes to
build/test YARN, as of say
https://amplab.cs.berkeley.edu/jenkins/view/Spark%20QA%20Test%20(Dashboard)/job/spark-master-test-maven-hadoop-2.7/1657/consoleFull
It's not much, but not trivial.
Yeah the thing is, everything depends on core really, so we should really
test everything _unless_ core has been changed. But we selectively build some
modules anyway as I suppose the PR builder is only to catch 99% of problems,
with the full Jenkins tests actually testing everything.
Yeah this came up because of Mesos and it seemed like YARN could use a
similar treatment since it's also a separable module and profile.
---
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]
