river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Firmstone <j...@zeus.net.au>
Subject Re: Debugging River (Was: Re: new release?)
Date Mon, 15 Nov 2010 00:16:49 GMT
Patricia Shanahan wrote:
> Peter Firmstone wrote:
>> Patricia Shanahan wrote:
>>> Peter Firmstone wrote:
>>>> Peter Firmstone wrote:
>>>>> Peter Firmstone wrote:
>>>>>> Patricia Shanahan wrote:
>>>>>>> On 11/13/2010 12:46 AM, Peter Firmstone wrote:
>>>>>>>> Patricia Shanahan wrote:
>>>>>>>>> On 11/12/2010 4:25 PM, Peter Firmstone wrote:
>>>>>>>>>> Patricia Shanahan wrote:
>>>>>>>>>>> On 11/12/2010 1:56 PM, Peter Firmstone wrote:
>>> ...
>>>>>>>>>>>> The failling tests are:
>>>>>>>>>>>>
>>>>>>>>>>>> 1. Jtreg: qa/jtreg/net/jini/url/httpmd/TestEqual.java
>>>>>>>>>>>> 2. QA: com/sun/jini/test/impl/start/ServiceStarterCreateBad
>>>>>>>>>>>> TransientServiceTest.td
>>>>>>>>>>>> 3. QA: com/sun/jini/test/impl/start/ServiceStarterCreateSha
>>>>>>>>>>>> redBadActServiceTest.td
>>>>>>>>>>>>
>>>>>>>>>>>> Note the QA tests pass with JDK 1.5 but fail
with JDK 1.6
>>>>>>>>>>>>
>>>>>>>>>>>> Build is compiled with 1.6.
>>>>>>>>>>> ...
>>>>>>>>>>>
>>>>>>>>>>> I can't reproduce the QA failures. I compiled
and ran with JDK
>>>>>>>>>>> 1.6.0_22, and with no differences between my
working River 
>>>>>>>>>>> and the
>>>>>>>>>>> trunk head. Any ideas on how to get them to happen?
>>> ...
>>>>
>>>> Well the good news is that with debugging turned on, the test still 
>>>> fails, so it's solvable, the bad news is, I haven't worked out why 
>>>> yet and I'm not going to have much time over the next week.  Will 
>>>> let you know how I go.
>>>
>>> It would be solvable regardless of being able to turn on debug - it is
>>> just a bit more convenient with debug.
>>>
>>> Combining this with your previous comment that policies may be 
>>> involved,
>>> I think this problem seems more like a case of failure depending on the
>>> previous test run history of the machine than depending on compiler
>>> version or timing.
>>>
>>> My next experiment, probably on Monday, will be to run the failing 
>>> tests
>>> in each of my Ubuntu partitions to see if any of them fail. If not, I
>>> may try setting up a clean new partition that has never run River
>>> before, and see what happens there.
>>>
>>> Patricia
>>>
>> The problem seems to be permission related, jdk 1.5 denies permission
>>
>> access: access denied (java.io.FilePermission 
>> /var/tmp/Mercury14589.config read)
>>
>> while jdk 1.6 allows:
>>
>> access: access allowed (java.io.FilePermission 
>> /var/tmp/Mercury13735.config read)
> ...
>
> Were both these runs done on the same machine?
>
> Thanks,
>
> Patricia
>
>
>
Yes.


Mime
View raw message