How can we add an ubuntu-15.04 target for that command? On Thu, Jan 14, 2016 at 2:48 PM, Andrew Musselman < [email protected]> wrote:
> Yes, thanks, removing the username worked. > > On Thu, Jan 14, 2016 at 2:38 PM, Konstantin Boudnik <[email protected]> > wrote: > >> On Thu, Jan 14, 2016 at 02:31PM, Andrew Musselman wrote: >> > Getting errors using a couple methods of building a package, anyone seen >> > these before? >> > >> > $ sudo docker run --rm -u jenkins:jenkins -v `pwd`:/ws --workdir /ws >> > bigtop/slaves:trunk-ubuntu-14.04 bash -l -c './gradlew allclean ; >> ./gradlew >> > bigtop-groovy-pkg' >> > % Total % Received % Xferd Average Speed Time Time Time >> > Current >> > Dload Upload Total Spent Left >> > Speed >> > 100 354 0 354 0 0 1195 0 --:--:-- --:--:-- --:--:-- >> > 1195 >> > 100 42.7M 100 42.7M 0 0 8640k 0 0:00:05 0:00:05 --:--:-- >> > 9797k >> > ~/.gradle/wrapper/dists/gradle-2.7-bin/50b53d4706e2955e697f548de257ad2a >> /ws >> > /ws >> > Starting a new Gradle Daemon for this build (subsequent builds will be >> > faster). >> > >> > FAILURE: Build failed with an exception. >> > >> > * What went wrong: >> > Failed to create parent directory >> > >> '/usr/share/gradle.home/caches/2.7/scripts/defaultBuildSourceScript_e6528ds75r98uqesruh04mz8k' >> > when creating directory >> > >> '/usr/share/gradle.home/caches/2.7/scripts/defaultBuildSourceScript_e6528ds75r98uqesruh04mz8k/cp_dsl' >> >> Looks like either: >> - you have an old ubuntu-14.04 images cached locally (try to docker pull >> if so) >> - we still haven't fixed the issue with the permissions on >> /usr/share/gradle/home dir. In which case simply run the process >> without -u jenkins:jenkins >> >> Hope it helps, >> Cos >> >> >> > >> > $ gradle bigtop-mahout-deb >> > :buildSrc:clean >> > :buildSrc:compileJava UP-TO-DATE >> > :buildSrc:compileGroovy >> > :buildSrc:processResources UP-TO-DATE >> > :buildSrc:classes >> > :buildSrc:jar >> > :buildSrc:assemble >> > :buildSrc:compileTestJava UP-TO-DATE >> > :buildSrc:compileTestGroovy >> > :buildSrc:processTestResources UP-TO-DATE >> > :buildSrc:testClasses >> > :buildSrc:test >> > >> > org.apache.bigtop.TestNullOutputStream > initializationError FAILED >> > java.lang.NoClassDefFoundError >> > Caused by: java.lang.ClassNotFoundException >> > >> > 1 test completed, 1 failed >> > :buildSrc:test FAILED >> > >> > FAILURE: Build failed with an exception. >> > >> > On Thu, Jan 14, 2016 at 1:45 PM, Andrew Musselman < >> > [email protected]> wrote: >> > >> > > Should I be building from master? >> > > >> > > $ gradle tasks --all >> > > :buildSrc:clean >> > > :buildSrc:compileJava UP-TO-DATE >> > > :buildSrc:compileGroovy >> > > :buildSrc:processResources UP-TO-DATE >> > > :buildSrc:classes >> > > :buildSrc:jar >> > > :buildSrc:assemble >> > > :buildSrc:compileTestJava UP-TO-DATE >> > > :buildSrc:compileTestGroovy >> > > :buildSrc:processTestResources UP-TO-DATE >> > > :buildSrc:testClasses >> > > :buildSrc:test >> > > >> > > org.apache.bigtop.TestNullOutputStream > initializationError FAILED >> > > java.lang.NoClassDefFoundError >> > > Caused by: java.lang.ClassNotFoundException >> > > >> > > 1 test completed, 1 failed >> > > :buildSrc:test FAILED >> > > >> > > >> > >
