Re: patch ready for review

thanks On Thu, Jan 14, 2016 at 2:30 PM, Konstantin Boudnik wrote: > Once the patch is ready you can simply trigger it into "Patch Available" > state > by clicking "Submit Patch" button in the JIRA. > > Cos > > On Thu, Jan 14, 2016 at 02:15PM, MrAsanjar . wrote: > > thanks in

Re: Error running `gradle tasks --all`

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 ;

[jira] [Created] (BIGTOP-2244) CI provisioner tests are failing after BIGTOP-2227 change

Konstantin Boudnik created BIGTOP-2244: -- Summary: CI provisioner tests are failing after BIGTOP-2227 change Key: BIGTOP-2244 URL: https://issues.apache.org/jira/browse/BIGTOP-2244 Project: Bigtop

Re: mahout-download fails

I have noticed errors like this as well. If I add "--stacktrace" to the arguments, I see that the Apache mirror returned a 403 for the URL. As Andrew says, doing a wget on the same exact URL works fine. Also, I'm pretty sure I've noticed that the error only occurs while I'm in the office on the

Re: mahout-download fails

If a release has been published just recently, then it might not be on all mirrors yet. That's the only explanation I have. Cos On Fri, Jan 15, 2016 at 12:11AM, Jonathan Kelly wrote: > I have noticed errors like this as well. If I add "--stacktrace" to the > arguments, I see that the Apache

[jira] [Created] (BIGTOP-2242) Running ./gradlew shouldn'e be failing because of unset JAVA_HOME

Konstantin Boudnik created BIGTOP-2242: -- Summary: Running ./gradlew shouldn'e be failing because of unset JAVA_HOME Key: BIGTOP-2242 URL: https://issues.apache.org/jira/browse/BIGTOP-2242

Re: Error running `gradle tasks --all`

How can we add an ubuntu-15.04 target for that command? On Thu, Jan 14, 2016 at 2:48 PM, Andrew Musselman < andrew.mussel...@gmail.com> wrote: > Yes, thanks, removing the username worked. > > On Thu, Jan 14, 2016 at 2:38 PM, Konstantin Boudnik > wrote: > >> On Thu, Jan 14, 2016

Re: Error running `gradle tasks --all`

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

Re: Error running `gradle tasks --all`

Yes, thanks, removing the username worked. On Thu, Jan 14, 2016 at 2:38 PM, Konstantin Boudnik 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

mahout-download fails

Even though `wget http://apache.osuosl.org//mahout/0.11.0//apache-mahout-distribution-0.11.0-src.tar.gz` succeeds, I get this error: $ ./gradlew mahout-download :buildSrc:compileJava UP-TO-DATE :buildSrc:compileGroovy UP-TO-DATE :buildSrc:processResources UP-TO-DATE :buildSrc:classes UP-TO-DATE

Re: Error running `gradle tasks --all`

We haven't just yet started supporting Ubuntu 15. Generally, it would require getting the base image, setting up toolchain, [making sure everything works, fixing toolchain/stack if needed]+, and then pushing it up to out dockerhub Cos On Thu, Jan 14, 2016 at 03:15PM, Andrew Musselman wrote: >

Re: mahout-download fails

Could you please publish your patch to the JIRA? And I suggest to move this discussion there as well. Cheers, Cos On Thu, Jan 14, 2016 at 03:37PM, Andrew Musselman wrote: > Even though `wget > http://apache.osuosl.org//mahout/0.11.0//apache-mahout-distribution-0.11.0-src.tar.gz` > succeeds, I

[jira] [Created] (BIGTOP-2243) :itest-common:test is broken without JAVA_HOME being set

Konstantin Boudnik created BIGTOP-2243: -- Summary: :itest-common:test is broken without JAVA_HOME being set Key: BIGTOP-2243 URL: https://issues.apache.org/jira/browse/BIGTOP-2243 Project: Bigtop

Re: Bigtop provisioner [Was: for other distros]

Hey guys. Looks like moving the smokes into the top-level had an interesting effect on the provisioner. BIGTOP-2244 explains the issue which was failing our CI smoke testing. Now all is back to blue again. However, looking into the provisioner jobs, like

[jira] [Created] (BIGTOP-2245) TestFuseHCFS might fall on '+' op. involving String and GString; class name is wrong

Konstantin Boudnik created BIGTOP-2245: -- Summary: TestFuseHCFS might fall on '+' op. involving String and GString; class name is wrong Key: BIGTOP-2245 URL: https://issues.apache.org/jira/browse/BIGTOP-2245

[jira] [Created] (BIGTOP-2246) Add smoke tests for HCFS

Konstantin Boudnik created BIGTOP-2246: -- Summary: Add smoke tests for HCFS Key: BIGTOP-2246 URL: https://issues.apache.org/jira/browse/BIGTOP-2246 Project: Bigtop Issue Type: Bug

Re: mahout-download fails

No, it's not related to new app versions. This happens any time I try (from my dev machine while on the corporate network) to build any app that downloads its source from the Apache mirror, which for some reason seems to be hardcoded to http://apache.osuosl.org. What's even weirder is that I have

[jira] [Created] (BIGTOP-2247) Expand HDFS smoke test suite

Konstantin Boudnik created BIGTOP-2247: -- Summary: Expand HDFS smoke test suite Key: BIGTOP-2247 URL: https://issues.apache.org/jira/browse/BIGTOP-2247 Project: Bigtop Issue Type: Bug

[jira] [Created] (BIGTOP-2241) "How to contribute" page needs to be updated

Konstantin Boudnik created BIGTOP-2241: -- Summary: "How to contribute" page needs to be updated Key: BIGTOP-2241 URL: https://issues.apache.org/jira/browse/BIGTOP-2241 Project: Bigtop

patch ready for review

thanks in advance https://issues.apache.org/jira/browse/BIGTOP-2240

Re: patch ready for review

Once the patch is ready you can simply trigger it into "Patch Available" state by clicking "Submit Patch" button in the JIRA. Cos On Thu, Jan 14, 2016 at 02:15PM, MrAsanjar . wrote: > thanks in advance > https://issues.apache.org/jira/browse/BIGTOP-2240 signature.asc Description: Digital

[jira] [Created] (BIGTOP-2240) Apache Hama build fails on ppc64le

Amir Sanjar created BIGTOP-2240: --- Summary: Apache Hama build fails on ppc64le Key: BIGTOP-2240 URL: https://issues.apache.org/jira/browse/BIGTOP-2240 Project: Bigtop Issue Type: Bug

Error running `gradle tasks --all`

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