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:
>
&
ext 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:
o: 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 J
Just a quick ping to see if this patch to remove the “-server” switch could get
into trunk?
Thanks,
Dan
Subject Re: Test Failures on ARM, maybe I'm missing setup?
DateTue, 05 Jan 2016 22:39:05 GMT
Thanks Dan, consider it removed.
Sent from my Samsung device.
Include original message
;danro...@gmail.com> wrote:
>
> Just a quick ping to see if this patch to remove the “-server” switch could
> get into trunk?
>
> Thanks,
> Dan
>
>
>
> Subject Re: Test Failures on ARM, maybe I'm missing setup?
> Date Tue, 05 Jan 2016 22:39:05 GMT
&g
il.com>
> Sent: 05/01/2016 08:20:52 am
> To: dev@river.apache.org
> Subject: Re: Test Failures on ARM, maybe I'm missing setup?
>
> Thanks Greg, and Peter. I was able to apply the “remove -server” fix to
> qaDefaults.properties, and the test ran fine on a Pi. I’ve attache
.
I guess I'm trying to make the case that just removing the “-server” arg is
acceptable. :)
Dan
> On Jan 5, 2016, at 11:03 AM, dev-digest-h...@river.apache.org wrote:
>
> From: Peter <j...@zeus.net.au <mailto:j...@zeus.net.au>>
> Subject: Re: Test Failures on ARM, maybe
Thanks Dan, consider it removed.
Sent from my Samsung device.
Include original message
Original message
From: Dan Rollo <danro...@gmail.com>
Sent: 06/01/2016 05:34:26 am
To: Cc: dev@river.apache.org
Subject: Re: Test Failures on ARM, maybe I'm missing setup?
I couldn’t find
261 to FINE
>>
>> Then please try again.
>>
>> You should find a detailed test report in the qa directory.
>>
>> Thanks,
>>
>> Peter.
>>
>> Sent from my Samsung device.
>>
>> Include original message
>> Original message
FINE
> also change lines 197 and 261 to FINE
>
> Then please try again.
>
> You should find a detailed test report in the qa directory.
>
> Thanks,
>
> Peter.
>
> Sent from my Samsung device.
>
> Include original message
> Original message
>
Thanks Greg, and Peter. I was able to apply the “remove -server” fix to
qaDefaults.properties, and the test ran fine on a Pi. I’ve attached a patch
with these fixes against trunk. If there is a better way to submit such a
patch, please point me in the right direction ( - dare I ask about git?
nt: 05/01/2016 08:20:52 am
To: dev@river.apache.org
Subject: Re: Test Failures on ARM, maybe I'm missing setup?
Thanks Greg, and Peter. I was able to apply the “remove -server” fix to
qaDefaults.properties, and the test ran fine on a Pi. I’ve attached a patch
with these fixes against
;
> Include original message
> ---- Original message ----
> From: Dan Rollo <danro...@gmail.com>
> Sent: 04/01/2016 01:47:41 pm
> To: dev@river.apache.org
> Subject: Test Failures on ARM, maybe I'm missing setup?
>
> I tried to follow the step
I tried to follow the steps here: https://river.apache.org/building-river.html,
but I probably missed something.
My first attempt to build things was to setup my own Jenkins build (on
RaspberryPi Model 2’s) using the ant target:
"hudson-aa-arm"
In case it matters, I’m using ant-1.9.4, and
:41 pm
To: dev@river.apache.org
Subject: Test Failures on ARM, maybe I'm missing setup?
I tried to follow the steps here: https://river.apache.org/building-river.html,
but I probably missed something.
My first attempt to build things was to setup my own Jenkins build (on
RaspberryPi Model 2’s)
Hi Dan:
Peter’s the expert on the new trunk (formerly qa-refactor-namespace), but
offhand, I don’t see why the arm build should be different from the regular
build - the only obvious thing is that it doesn’t build the rmi stubs, which
really shouldn’t be a big deal, since they’re not needed
16 matches
Mail list logo