Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/8069#issuecomment-132481119
Workers that are already fixed are (along with a successfully compiled
build):
worker-02:
https://amplab.cs.berkeley.edu/jenkins/job/Spark-Master-SBT/3288/AMPLAB_JENKINS_BUILD_PROFILE=hadoop2.3,label=spark-test/console
worker-06:
https://amplab.cs.berkeley.edu/jenkins/job/Spark-Master-SBT/3288/AMPLAB_JENKINS_BUILD_PROFILE=hadoop1.0,label=spark-test/console
worker-08:
https://amplab.cs.berkeley.edu/jenkins/job/Spark-Master-SBT/3288/AMPLAB_JENKINS_BUILD_PROFILE=hadoop2.0,label=spark-test/console
On Wed, Aug 19, 2015 at 12:43 AM, Tathagata Das <[email protected]> wrote:
> The issues is actually SBT failing to resolve the artifact in the m2 cache
> even though the artifact is present. Basically the ivy2 cache of jboss
> needs to blown away.
>
> I am slowly fixing the issue on the jenkins workers. Since I am not able
> to access the Jenkins workers directly (ssh access not working for me), I
> am leveraging the Spark SBT master build to blow away cached jboss. And
> whatever worker it is running, that worker is getting fixed. Here is what
> fixes it.
>
> rm -rf /home/jenkins/.ivy2/cache/org.jboss*
> rm -rf /home/jenkins/.ivy2/cache/junit*
>
> I have it added in the Spark-SBT-master -
> https://amplab.cs.berkeley.edu/jenkins/job/Spark-Master-SBT/configure
> If you can login into the workers, would you mind running these two lines
> on each of them?
>
>
> On Wed, Aug 19, 2015 at 12:16 AM, Shivaram Venkataraman <
> [email protected]> wrote:
>
>> @srowen <https://github.com/srowen> @tdas <https://github.com/tdas> It
>> looks like this PR somehow changed the dependency tree and affected the
>> documentation build that happens as a cron job on Jenkins.
>>
>> The error log at
>>
https://amplab.cs.berkeley.edu/jenkins/view/Spark-Packaging/job/Spark-Master-Docs/690/consoleFull
>> is a run that happened after this PR and
>>
https://amplab.cs.berkeley.edu/jenkins/view/Spark-Packaging/job/Spark-Master-Docs/689/consoleFull
>> is a run from before
>>
>> It looks like this PR somehow introduces a dependency on netty 3.2.2
>> through mqtt, curator etc.
>>
>> Note: Unresolved dependencies path:�
>> org.jboss.netty:netty:3.2.2.Final�
>> +-org.apache.zookeeper:zookeeper:3.4.5
((com.typesafe.sbt.pom.MavenHelper)
>> +- org.apache.curator:curator-client:2.4.0�
>> +- org.apache.curator:curator-framework:2.4.0�
>> +- org.apache.curator:curator-recipes:2.4.0
((com.typesafe.sbt.pom.MavenHelper)
>> +- org.apache.spark:spark-core_2.10:1.5.0-SNAPSHOT�
>> +- org.apache.spark:spark-streaming_2.10:1.5.0-SNAPSHOT
((com.typesafe.sbt.pom.MavenHelper)
>> +- org.apache.spark:spark-streaming-mqtt_2.10:1.5.0-SNAPSHOT
>> +- org.apache.spark:spark-streaming-mqtt-assembly_2.10:1.5.0-SNAPSHOT�
>>
>> Did some exclude rules change or something like that ?
>>
>> cc @rxin <https://github.com/rxin>
>>
>> â
>> Reply to this email directly or view it on GitHub
>> <https://github.com/apache/spark/pull/8069#issuecomment-132470800>.
>>
>
>
---
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]
