jtreg is installed on hudson, but installed incorrectly, unfortunately it won't run until that's fixed. I run it locally on a regular basis, some tests fail on windows due to path issues. Also there are inconsistencies between hudson node configurations that require specific versions of ant, rather than just ant-latest.
There are a lot of build failures caused by hudson node configuration differences. Regards, Peter. Sent from my Samsung device. Include original message ---- Original message ---- From: Greg Trasuk <tras...@stratuscom.com> Sent: 27/01/2016 01:59:38 am To: dev@river.apache.org Subject: Re: Test Failures on ARM, maybe I'm missing setup? Hi Dan: Peter would be the one to comment on that - he setup the Jenkins job at builds.apache.org. I’m not actually sure it runs the jtreg tests, because I don’t know if jtreg is installed on the Apache Jenkins instance. Cheers, Greg > On Jan 26, 2016, at 10:51 AM, Dan Rollo <danro...@gmail.com> wrote: > > Thanks Greg. That’s got my local CI build passing. > > Now I just need to figure out which is the best target to call for my little >CI build. > > Also wondering how best to have the test results displayed. (HTML publisher >does OK for the text file test results (qa/results…), but I’m wondering how >Jenkins at apache is setup to detect/publish jtreg test success/failure). > > Dan > >> >> >> Subject: Re: Test Failures on ARM, maybe I'm missing setup? >> Date: January 21, 2016 at 11:10:14 PM EST >> To: dev@river.apache.org <mailto:dev@river.apache.org> >> >> >> Hi Dan: >> >> I couldn’t find your exact patch (might have been suppressed by the list), >>but I did the change to qaDefaults.properties manually, and said it was your >>patch in the commit message. >> >> ‘svn update’ and give it a try! >> >> Cheers, >> >> Greg Trasuk
