You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bigtop.apache.org by "Konstantin Boudnik (JIRA)" <ji...@apache.org> on 2015/10/27 19:57:27 UTC

[jira] [Commented] (BIGTOP-2100) Build from source errors out at test stage

    [ https://issues.apache.org/jira/browse/BIGTOP-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14976966#comment-14976966 ] 

Konstantin Boudnik commented on BIGTOP-2100:
--------------------------------------------

That's a bit weird, because at this point gradle build is used 100s times a day everywhere. I just have tried to reproduce it on the latest trunk and everything seems to be fine:
{code}
:buildSrc:testClasses
:buildSrc:test
:buildSrc:check
:buildSrc:build
{code}
What Gradle version are you using? We are on 2.7 and the wrapper script is on 2.7.
Also, if you look at the test in question - it doesn't have any dependencies at all. I would suggest to remove {{.gradle}} directory in your bigtop workspace and perhaps clean up {{~/.gradle/}}

> Build from source errors out at test stage
> ------------------------------------------
>
>                 Key: BIGTOP-2100
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-2100
>             Project: Bigtop
>          Issue Type: Bug
>    Affects Versions: 1.0.0
>         Environment: Ubuntu 14.04 (trusty)
>            Reporter: Tharindu Denuwara
>
> I downloaded the source and tried building it using the instruction in BUILDING.txt, but found that it failed on the tests.
> This is the command I used:
> gradle deb --info
> This is an excerpt of the output I got:
> Gradle Worker 2 finished executing tests.
> org.apache.bigtop.TestBuildUtils > initializationError FAILED
>     java.lang.NoClassDefFoundError: org/hamcrest/SelfDescribing
>         Caused by:
>         java.lang.ClassNotFoundException: org.hamcrest.SelfDescribing
> org.apache.bigtop.TestNullOutputStream > initializationError FAILED
>     java.lang.NoClassDefFoundError: org/hamcrest/SelfDescribing
> After some googling, I found that this happens when a dependency is not properly specified. Is there any way I can get around this?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)