You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@river.apache.org by Patricia Shanahan <pa...@acm.org> on 2010/07/09 04:52:04 UTC
QA tests and spaces in file names
On of the simplifying steps I took to try to set up River development on
a Windows box was use of a space-free path. I have since retested under
"My Documents" and get QA test failures of the form:
[java] com.sun.jini.qa.harness.TestException:
[java]
getResource(com/sun/jini/test/spec/loader/util/resources/files/file02)
[java]
returned:jar:file:/C:/Documents%20and%20Settings/Administrator/My%20Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
[java] expected:jar:file:/C:/Documents and
Settings/Administrator/My
Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
[java] at
com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.testCase(Unknown
Source)
[java] at
com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.run(Unknown
Source)
[java] at com.sun.jini.qa.harness.MasterTest.doTest(Unknown Source)
[java] at com.sun.jini.qa.harness.MasterTest.main(Unknown Source)
The expected URL leaves the spaces as spaces. The returned URL has the
spaces replaced, as is normal inside a URL, by %20.
Patricia
Re: QA tests and spaces in file names
Posted by Patricia Shanahan <pa...@acm.org>.
There was a problem with the path - it needs the word "trunk". Here is
my latest build.properties:
river.home=c:/apache/river/jtsk/trunk
jtreg.home=c:/apache/jtreg
jtreg.dir=C:/apache/river/jtsk/trunk/qa/jtreg
jdk1.5.home=C:/Program Files (x86)/Java/jdk1.5.0_22
With that, I'm back to not finding com.sun.jini.action as the first error:
[jtreg]
C:\apache\river\jtsk\trunk\qa\jtreg\com\sun\jini\action\catchSecurityException\CatchSecurityException.java:30:
package com.sun.jini.action does not exist
[jtreg] import com.sun.jini.action.GetBooleanAction;
Patricia
On 7/10/2010 6:44 AM, Patricia Shanahan wrote:
> I have a TEST.ROOT in my jtreg.dir, with the right contents, so we still
> have a failure to find files that exist. Here are the current contents
> of my /cygdrive/c/apache/river/jtsk/trunk/qa/build.properties:
>
> river.home=c:/apache/river/jtsk/trunk
> jtreg.home=c:/apache/jtreg
> jtreg.dir=C:\\apache\\river\\jtsk\\qa\\jtreg
> jdk1.5.home=C:\\Program Files (x86)\\Java\\jdk1.5.0_22
>
> (Either \\ or / can be used as the path separator in a build.properties
> file on Windows. A single / is treated as an escape character.)
>
> Patricia
>
>
> On 7/10/2010 5:56 AM, Peter Firmstone wrote:
>> TEST.ROOT is a text file in the C:\apache\river\jtsk\qa\jtreg directory.
>>
>> $ cat TEST.ROOT
>> # This file identifies the root of the test-suite hierarchy.
>> # It also contains test-suite configuration information.
>> # DO NOT EDIT without first contacting jdk-regtest@eng.
>>
>> # The list of keywords supported in this test suite
>> keys=2d dnd i18n
>>
>>
>> Patricia Shanahan wrote:
>>> Promising. I got error messages at first because I forgot to double up
>>> the "/" characters, so it was paying attention to the jtreg.dir line.
>>> Once I fixed that it went to:
>>>
>>> Buildfile: C:\apache\river\jtsk\trunk\qa\build.xml
>>>
>>> jtreg:
>>> [mkdir] Created dir: C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
>>> [move] Moving 4 files to C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
>>> [move] Moving 1 file to C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
>>> [move] Moving 1 file to C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
>>>
>>> BUILD FAILED
>>> C:\apache\river\jtsk\trunk\qa\build.xml:156: Cannot determine test
>>> suite from test (is TEST.ROOT missing?):
>>> C:\apache\river\jtsk\qa\jtreg\JTlib-tmp\concurrent-policy-util.jar
>>>
>>> Total time: 1 second
>>>
>>>
>>> What do you think it would like for TEST.ROOT?
>>>
>>>
>>> On 7/9/2010 11:55 PM, Peter Firmstone wrote:
>>>> Try adding this to your build.properties file:
>>>>
>>>> jtreg.dir=C:\apache\river\jtsk\qa\jtreg
>>>>
>>>> Peter.
>>>>
>>>> Patricia Shanahan wrote:
>>>>> Yes, I ran it in the root directory.
>>>>>
>>>>>
>>>>> Patricia
>>>>>
>>>>> On Jul 9, 2010, at 21:35, Peter Firmstone <ji...@zeus.net.au> wrote:
>>>>>
>>>>>> It appears as though it can't see the jar archives in the directory:
>>>>>>
>>>>>> C;\apache\river\jtsk\trunk\lib\
>>>>>>
>>>>>> The missing class is from jsk-platform.jar
>>>>>>
>>>>>> Did you run ant all.build first?
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> Peter.
>>>>>>
>>>>>> Patricia Shanahan wrote:
>>>>>>> Sure:
>>>>>>>
>>>>>>> http://www.patriciashanahan.com/apache/myJTREGLog.txt
>>>>>>>
>>>>>>> Patricia
>>>>>>>
>>>>>>>
>>>>>>> On 7/9/2010 7:59 PM, Peter Firmstone wrote:
>>>>>>>> Can you dump the output to a text file and submit it?
>>>>>>>>
>>>>>>>> Peter.
>>>>>>>>
>>>>>>>> Patricia Shanahan wrote:
>>>>>>>>> I tried that. It didn't seem to make any difference.
>>>>>>>>>
>>>>>>>>> Patricia
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 7/9/2010 4:48 PM, Peter Firmstone wrote:
>>>>>>>>>> Try copying your existing build.properties file to the qa
>>>>>>>>>> directory,
>>>>>>>>>> just for now.
>>>>>>>>>>
>>>>>>>>>> Then try the jtreg tests again too.
>>>>>>>>>>
>>>>>>>>>> Cheers,
>>>>>>>>>>
>>>>>>>>>> Peter.
>>>>>>>>>>
>>>>>>>>>> Patricia Shanahan wrote:
>>>>>>>>>>> The problem seems to be a classpath issue when compiling the
>>>>>>>>>>> tests. I
>>>>>>>>>>> get messages of the form:
>>>>>>>>>>>
>>>>>>>>>>> C:\\apache\\river\\jtsk\\trunk\\qa\\jtreg\\com\\sun\\jini\\action\\catchSecurityException\\CatchSecurityException.java:30:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> package com.sun.jini.action does not exist
>>>>>>>>>>> import com.sun.jini.action.GetBooleanAction;
>>>>>>>>>>>
>>>>>>>>>>> Do I need another build.properties file in the qa directory?
>>>>>>>>>>> If so,
>>>>>>>>>>> what should it contain?
>>>>>>>>>>>
>>>>>>>>>>> Patricia
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On 7/9/2010 4:04 AM, Peter Firmstone wrote:
>>>>>>>>>>>> Have you tried the jtreg tests?
>>>>>>>>>>>>
>>>>>>>>>>>> The results of the jtreg tests will appear under trunk/qa/jtreg
>>>>>>>>>>>>
>>>>>>>>>>>> jtreg constructs a web page index with detailed result pages
>>>>>>>>>>>> for
>>>>>>>>>>>> failed
>>>>>>>>>>>> tests.
>>>>>>>>>>>>
>>>>>>>>>>>> Cheers,
>>>>>>>>>>>>
>>>>>>>>>>>> Peter.
>>>>>>>>>>>>
>>>>>>>>>>>> Patricia Shanahan wrote:
>>>>>>>>>>>>> On of the simplifying steps I took to try to set up River
>>>>>>>>>>>>> development
>>>>>>>>>>>>> on a Windows box was use of a space-free path. I have since
>>>>>>>>>>>>> retested
>>>>>>>>>>>>> under "My Documents" and get QA test failures of the form:
>>>>>>>>>>>>>
>>>>>>>>>>>>> [java] com.sun.jini.qa.harness.TestException:
>>>>>>>>>>>>> [java]
>>>>>>>>>>>>> getResource(com/sun/jini/test/spec/loader/util/resources/files/file02)
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> [java]
>>>>>>>>>>>>> returned:jar:file:/C:/Documents%20and%20Settings/Administrator/My%20Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> [java] expected:jar:file:/C:/Documents and
>>>>>>>>>>>>> Settings/Administrator/My
>>>>>>>>>>>>> Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> [java] at
>>>>>>>>>>>>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.testCase(Unknown
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Source)
>>>>>>>>>>>>> [java] at
>>>>>>>>>>>>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.run(Unknown
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Source)
>>>>>>>>>>>>> [java] at com.sun.jini.qa.harness.MasterTest.doTest(Unknown
>>>>>>>>>>>>> Source)
>>>>>>>>>>>>> [java] at com.sun.jini.qa.harness.MasterTest.main(Unknown
>>>>>>>>>>>>> Source)
>>>>>>>>>>>>>
>>>>>>>>>>>>> The expected URL leaves the spaces as spaces. The returned URL
>>>>>>>>>>>>> has
>>>>>>>>>>>>> the
>>>>>>>>>>>>> spaces replaced, as is normal inside a URL, by %20.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Patricia
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
Re: QA tests and spaces in file names
Posted by Patricia Shanahan <pa...@acm.org>.
I have a TEST.ROOT in my jtreg.dir, with the right contents, so we still
have a failure to find files that exist. Here are the current contents
of my /cygdrive/c/apache/river/jtsk/trunk/qa/build.properties:
river.home=c:/apache/river/jtsk/trunk
jtreg.home=c:/apache/jtreg
jtreg.dir=C:\\apache\\river\\jtsk\\qa\\jtreg
jdk1.5.home=C:\\Program Files (x86)\\Java\\jdk1.5.0_22
(Either \\ or / can be used as the path separator in a build.properties
file on Windows. A single / is treated as an escape character.)
Patricia
On 7/10/2010 5:56 AM, Peter Firmstone wrote:
> TEST.ROOT is a text file in the C:\apache\river\jtsk\qa\jtreg directory.
>
> $ cat TEST.ROOT
> # This file identifies the root of the test-suite hierarchy.
> # It also contains test-suite configuration information.
> # DO NOT EDIT without first contacting jdk-regtest@eng.
>
> # The list of keywords supported in this test suite
> keys=2d dnd i18n
>
>
> Patricia Shanahan wrote:
>> Promising. I got error messages at first because I forgot to double up
>> the "/" characters, so it was paying attention to the jtreg.dir line.
>> Once I fixed that it went to:
>>
>> Buildfile: C:\apache\river\jtsk\trunk\qa\build.xml
>>
>> jtreg:
>> [mkdir] Created dir: C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
>> [move] Moving 4 files to C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
>> [move] Moving 1 file to C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
>> [move] Moving 1 file to C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
>>
>> BUILD FAILED
>> C:\apache\river\jtsk\trunk\qa\build.xml:156: Cannot determine test
>> suite from test (is TEST.ROOT missing?):
>> C:\apache\river\jtsk\qa\jtreg\JTlib-tmp\concurrent-policy-util.jar
>>
>> Total time: 1 second
>>
>>
>> What do you think it would like for TEST.ROOT?
>>
>>
>> On 7/9/2010 11:55 PM, Peter Firmstone wrote:
>>> Try adding this to your build.properties file:
>>>
>>> jtreg.dir=C:\apache\river\jtsk\qa\jtreg
>>>
>>> Peter.
>>>
>>> Patricia Shanahan wrote:
>>>> Yes, I ran it in the root directory.
>>>>
>>>>
>>>> Patricia
>>>>
>>>> On Jul 9, 2010, at 21:35, Peter Firmstone <ji...@zeus.net.au> wrote:
>>>>
>>>>> It appears as though it can't see the jar archives in the directory:
>>>>>
>>>>> C;\apache\river\jtsk\trunk\lib\
>>>>>
>>>>> The missing class is from jsk-platform.jar
>>>>>
>>>>> Did you run ant all.build first?
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Peter.
>>>>>
>>>>> Patricia Shanahan wrote:
>>>>>> Sure:
>>>>>>
>>>>>> http://www.patriciashanahan.com/apache/myJTREGLog.txt
>>>>>>
>>>>>> Patricia
>>>>>>
>>>>>>
>>>>>> On 7/9/2010 7:59 PM, Peter Firmstone wrote:
>>>>>>> Can you dump the output to a text file and submit it?
>>>>>>>
>>>>>>> Peter.
>>>>>>>
>>>>>>> Patricia Shanahan wrote:
>>>>>>>> I tried that. It didn't seem to make any difference.
>>>>>>>>
>>>>>>>> Patricia
>>>>>>>>
>>>>>>>>
>>>>>>>> On 7/9/2010 4:48 PM, Peter Firmstone wrote:
>>>>>>>>> Try copying your existing build.properties file to the qa
>>>>>>>>> directory,
>>>>>>>>> just for now.
>>>>>>>>>
>>>>>>>>> Then try the jtreg tests again too.
>>>>>>>>>
>>>>>>>>> Cheers,
>>>>>>>>>
>>>>>>>>> Peter.
>>>>>>>>>
>>>>>>>>> Patricia Shanahan wrote:
>>>>>>>>>> The problem seems to be a classpath issue when compiling the
>>>>>>>>>> tests. I
>>>>>>>>>> get messages of the form:
>>>>>>>>>>
>>>>>>>>>> C:\\apache\\river\\jtsk\\trunk\\qa\\jtreg\\com\\sun\\jini\\action\\catchSecurityException\\CatchSecurityException.java:30:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> package com.sun.jini.action does not exist
>>>>>>>>>> import com.sun.jini.action.GetBooleanAction;
>>>>>>>>>>
>>>>>>>>>> Do I need another build.properties file in the qa directory?
>>>>>>>>>> If so,
>>>>>>>>>> what should it contain?
>>>>>>>>>>
>>>>>>>>>> Patricia
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On 7/9/2010 4:04 AM, Peter Firmstone wrote:
>>>>>>>>>>> Have you tried the jtreg tests?
>>>>>>>>>>>
>>>>>>>>>>> The results of the jtreg tests will appear under trunk/qa/jtreg
>>>>>>>>>>>
>>>>>>>>>>> jtreg constructs a web page index with detailed result pages for
>>>>>>>>>>> failed
>>>>>>>>>>> tests.
>>>>>>>>>>>
>>>>>>>>>>> Cheers,
>>>>>>>>>>>
>>>>>>>>>>> Peter.
>>>>>>>>>>>
>>>>>>>>>>> Patricia Shanahan wrote:
>>>>>>>>>>>> On of the simplifying steps I took to try to set up River
>>>>>>>>>>>> development
>>>>>>>>>>>> on a Windows box was use of a space-free path. I have since
>>>>>>>>>>>> retested
>>>>>>>>>>>> under "My Documents" and get QA test failures of the form:
>>>>>>>>>>>>
>>>>>>>>>>>> [java] com.sun.jini.qa.harness.TestException:
>>>>>>>>>>>> [java]
>>>>>>>>>>>> getResource(com/sun/jini/test/spec/loader/util/resources/files/file02)
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> [java]
>>>>>>>>>>>> returned:jar:file:/C:/Documents%20and%20Settings/Administrator/My%20Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> [java] expected:jar:file:/C:/Documents and
>>>>>>>>>>>> Settings/Administrator/My
>>>>>>>>>>>> Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> [java] at
>>>>>>>>>>>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.testCase(Unknown
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Source)
>>>>>>>>>>>> [java] at
>>>>>>>>>>>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.run(Unknown
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Source)
>>>>>>>>>>>> [java] at com.sun.jini.qa.harness.MasterTest.doTest(Unknown
>>>>>>>>>>>> Source)
>>>>>>>>>>>> [java] at com.sun.jini.qa.harness.MasterTest.main(Unknown
>>>>>>>>>>>> Source)
>>>>>>>>>>>>
>>>>>>>>>>>> The expected URL leaves the spaces as spaces. The returned URL
>>>>>>>>>>>> has
>>>>>>>>>>>> the
>>>>>>>>>>>> spaces replaced, as is normal inside a URL, by %20.
>>>>>>>>>>>>
>>>>>>>>>>>> Patricia
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>
>>
>
>
Re: QA tests and spaces in file names
Posted by Peter Firmstone <ji...@zeus.net.au>.
TEST.ROOT is a text file in the C:\apache\river\jtsk\qa\jtreg directory.
$ cat TEST.ROOT
# This file identifies the root of the test-suite hierarchy.
# It also contains test-suite configuration information.
# DO NOT EDIT without first contacting jdk-regtest@eng.
# The list of keywords supported in this test suite
keys=2d dnd i18n
Patricia Shanahan wrote:
> Promising. I got error messages at first because I forgot to double up
> the "/" characters, so it was paying attention to the jtreg.dir line.
> Once I fixed that it went to:
>
> Buildfile: C:\apache\river\jtsk\trunk\qa\build.xml
>
> jtreg:
> [mkdir] Created dir: C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
> [move] Moving 4 files to C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
> [move] Moving 1 file to C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
> [move] Moving 1 file to C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
>
> BUILD FAILED
> C:\apache\river\jtsk\trunk\qa\build.xml:156: Cannot determine test
> suite from test (is TEST.ROOT missing?):
> C:\apache\river\jtsk\qa\jtreg\JTlib-tmp\concurrent-policy-util.jar
>
> Total time: 1 second
>
>
> What do you think it would like for TEST.ROOT?
>
>
> On 7/9/2010 11:55 PM, Peter Firmstone wrote:
>> Try adding this to your build.properties file:
>>
>> jtreg.dir=C:\apache\river\jtsk\qa\jtreg
>>
>> Peter.
>>
>> Patricia Shanahan wrote:
>>> Yes, I ran it in the root directory.
>>>
>>>
>>> Patricia
>>>
>>> On Jul 9, 2010, at 21:35, Peter Firmstone <ji...@zeus.net.au> wrote:
>>>
>>>> It appears as though it can't see the jar archives in the directory:
>>>>
>>>> C;\apache\river\jtsk\trunk\lib\
>>>>
>>>> The missing class is from jsk-platform.jar
>>>>
>>>> Did you run ant all.build first?
>>>>
>>>> Cheers,
>>>>
>>>> Peter.
>>>>
>>>> Patricia Shanahan wrote:
>>>>> Sure:
>>>>>
>>>>> http://www.patriciashanahan.com/apache/myJTREGLog.txt
>>>>>
>>>>> Patricia
>>>>>
>>>>>
>>>>> On 7/9/2010 7:59 PM, Peter Firmstone wrote:
>>>>>> Can you dump the output to a text file and submit it?
>>>>>>
>>>>>> Peter.
>>>>>>
>>>>>> Patricia Shanahan wrote:
>>>>>>> I tried that. It didn't seem to make any difference.
>>>>>>>
>>>>>>> Patricia
>>>>>>>
>>>>>>>
>>>>>>> On 7/9/2010 4:48 PM, Peter Firmstone wrote:
>>>>>>>> Try copying your existing build.properties file to the qa
>>>>>>>> directory,
>>>>>>>> just for now.
>>>>>>>>
>>>>>>>> Then try the jtreg tests again too.
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>>
>>>>>>>> Peter.
>>>>>>>>
>>>>>>>> Patricia Shanahan wrote:
>>>>>>>>> The problem seems to be a classpath issue when compiling the
>>>>>>>>> tests. I
>>>>>>>>> get messages of the form:
>>>>>>>>>
>>>>>>>>> C:\\apache\\river\\jtsk\\trunk\\qa\\jtreg\\com\\sun\\jini\\action\\catchSecurityException\\CatchSecurityException.java:30:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> package com.sun.jini.action does not exist
>>>>>>>>> import com.sun.jini.action.GetBooleanAction;
>>>>>>>>>
>>>>>>>>> Do I need another build.properties file in the qa directory?
>>>>>>>>> If so,
>>>>>>>>> what should it contain?
>>>>>>>>>
>>>>>>>>> Patricia
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 7/9/2010 4:04 AM, Peter Firmstone wrote:
>>>>>>>>>> Have you tried the jtreg tests?
>>>>>>>>>>
>>>>>>>>>> The results of the jtreg tests will appear under trunk/qa/jtreg
>>>>>>>>>>
>>>>>>>>>> jtreg constructs a web page index with detailed result pages for
>>>>>>>>>> failed
>>>>>>>>>> tests.
>>>>>>>>>>
>>>>>>>>>> Cheers,
>>>>>>>>>>
>>>>>>>>>> Peter.
>>>>>>>>>>
>>>>>>>>>> Patricia Shanahan wrote:
>>>>>>>>>>> On of the simplifying steps I took to try to set up River
>>>>>>>>>>> development
>>>>>>>>>>> on a Windows box was use of a space-free path. I have since
>>>>>>>>>>> retested
>>>>>>>>>>> under "My Documents" and get QA test failures of the form:
>>>>>>>>>>>
>>>>>>>>>>> [java] com.sun.jini.qa.harness.TestException:
>>>>>>>>>>> [java]
>>>>>>>>>>> getResource(com/sun/jini/test/spec/loader/util/resources/files/file02)
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> [java]
>>>>>>>>>>> returned:jar:file:/C:/Documents%20and%20Settings/Administrator/My%20Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> [java] expected:jar:file:/C:/Documents and
>>>>>>>>>>> Settings/Administrator/My
>>>>>>>>>>> Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> [java] at
>>>>>>>>>>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.testCase(Unknown
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Source)
>>>>>>>>>>> [java] at
>>>>>>>>>>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.run(Unknown
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Source)
>>>>>>>>>>> [java] at com.sun.jini.qa.harness.MasterTest.doTest(Unknown
>>>>>>>>>>> Source)
>>>>>>>>>>> [java] at com.sun.jini.qa.harness.MasterTest.main(Unknown
>>>>>>>>>>> Source)
>>>>>>>>>>>
>>>>>>>>>>> The expected URL leaves the spaces as spaces. The returned URL
>>>>>>>>>>> has
>>>>>>>>>>> the
>>>>>>>>>>> spaces replaced, as is normal inside a URL, by %20.
>>>>>>>>>>>
>>>>>>>>>>> Patricia
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>>
>
>
Re: QA tests and spaces in file names
Posted by Peter Firmstone <ji...@zeus.net.au>.
Hi Patricia,
I've been a little busy, it's been some time since I ran jtreg from the
command line, I will get back to you with the correct arguments, it's
not that simple. In the mean time if your curious, the ant jtreg target
should give you an idea.
You'll need to manually move the files as per the ant scripts, then
execute the command with all the required options. I'm pretty sure
you'll also need to set JT_HOME and JDK_HOME environment variables.
I'll get back to you, but probably not until the weekend.
Cheers,
Peter.
Patricia Shanahan wrote:
> Correct. I did try using only "/" as path separator, and it still
> failed. Here is my latest build.properties:
>
> bash-3.2$ pwd
> /cygdrive/c/apache/river/jtsk/trunk/qa
> bash-3.2$ cat build.properties
> river.home=c:/apache/river/jtsk/trunk
> jtreg.home=c:/apache/jtreg
> jtreg.dir=C:/apache/river/jtsk/trunk/qa/jtreg
> jdk1.5.home=C:/Program Files (x86)/Java/jdk1.5.0_22
>
> The output is in http://www.patriciashanahan.com/apache/myJTREGLog.txt
>
> Maybe somebody could make available to me the output from a correct
> regression test? Part of my problem is that, being unfamiliar with
> River, the Apache development flow in general, and JTreg in
> particular, I don't know what output to expect.
>
> The problems look to me rather like a compile-time classpath problem -
> files are found if the scripts are looking for them directly, but the
> compiler cannot find packages for import statements.
>
> Thanks for any suggestions,
>
> Patricia
>
>
> On 7/12/2010 7:57 AM, Gregg Wonderly wrote:
>> As a general rule, there is no reason to use '\' in java paths that are
>> passed into any class that uses the path inside of the JVM. Only when
>> you use Runtime.exec() et.al. do you need to worry about '/' vs '\'.
>> Windows, a long time ago, recognized '/' internally as a path separator,
>> because only the 'shell' was dealing with '/' as an option delimiter.
>>
>> It makes life a lot easier to just use '/' for java.lang.File paths and
>> in particular, it simplifies property file and other text usage where
>> '\' is interpreted by the class as a special character.
>>
>> Gregg Wonderly
>>
>> Patricia Shanahan wrote:
>>> Promising. I got error messages at first because I forgot to double up
>>> the "/" characters, so it was paying attention to the jtreg.dir line.
>>> Once I fixed that it went to:
>>>
>>> Buildfile: C:\apache\river\jtsk\trunk\qa\build.xml
>>>
>>> jtreg:
>>> [mkdir] Created dir: C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
>>> [move] Moving 4 files to C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
>>> [move] Moving 1 file to C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
>>> [move] Moving 1 file to C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
>>>
>>> BUILD FAILED
>>> C:\apache\river\jtsk\trunk\qa\build.xml:156: Cannot determine test
>>> suite from test (is TEST.ROOT missing?):
>>> C:\apache\river\jtsk\qa\jtreg\JTlib-tmp\concurrent-policy-util.jar
>>>
>>> Total time: 1 second
>>>
>>>
>>> What do you think it would like for TEST.ROOT?
>>>
>>>
>>> On 7/9/2010 11:55 PM, Peter Firmstone wrote:
>>>> Try adding this to your build.properties file:
>>>>
>>>> jtreg.dir=C:\apache\river\jtsk\qa\jtreg
>>>>
>>>> Peter.
>>>>
>>>> Patricia Shanahan wrote:
>>>>> Yes, I ran it in the root directory.
>>>>>
>>>>>
>>>>> Patricia
>>>>>
>>>>> On Jul 9, 2010, at 21:35, Peter Firmstone <ji...@zeus.net.au> wrote:
>>>>>
>>>>>> It appears as though it can't see the jar archives in the directory:
>>>>>>
>>>>>> C;\apache\river\jtsk\trunk\lib\
>>>>>>
>>>>>> The missing class is from jsk-platform.jar
>>>>>>
>>>>>> Did you run ant all.build first?
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> Peter.
>>>>>>
>>>>>> Patricia Shanahan wrote:
>>>>>>> Sure:
>>>>>>>
>>>>>>> http://www.patriciashanahan.com/apache/myJTREGLog.txt
>>>>>>>
>>>>>>> Patricia
>>>>>>>
>>>>>>>
>>>>>>> On 7/9/2010 7:59 PM, Peter Firmstone wrote:
>>>>>>>> Can you dump the output to a text file and submit it?
>>>>>>>>
>>>>>>>> Peter.
>>>>>>>>
>>>>>>>> Patricia Shanahan wrote:
>>>>>>>>> I tried that. It didn't seem to make any difference.
>>>>>>>>>
>>>>>>>>> Patricia
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 7/9/2010 4:48 PM, Peter Firmstone wrote:
>>>>>>>>>> Try copying your existing build.properties file to the qa
>>>>>>>>>> directory,
>>>>>>>>>> just for now.
>>>>>>>>>>
>>>>>>>>>> Then try the jtreg tests again too.
>>>>>>>>>>
>>>>>>>>>> Cheers,
>>>>>>>>>>
>>>>>>>>>> Peter.
>>>>>>>>>>
>>>>>>>>>> Patricia Shanahan wrote:
>>>>>>>>>>> The problem seems to be a classpath issue when compiling the
>>>>>>>>>>> tests. I
>>>>>>>>>>> get messages of the form:
>>>>>>>>>>>
>>>>>>>>>>> C:\\apache\\river\\jtsk\\trunk\\qa\\jtreg\\com\\sun\\jini\\action\\catchSecurityException\\CatchSecurityException.java:30:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> package com.sun.jini.action does not exist
>>>>>>>>>>> import com.sun.jini.action.GetBooleanAction;
>>>>>>>>>>>
>>>>>>>>>>> Do I need another build.properties file in the qa directory?
>>>>>>>>>>> If so,
>>>>>>>>>>> what should it contain?
>>>>>>>>>>>
>>>>>>>>>>> Patricia
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On 7/9/2010 4:04 AM, Peter Firmstone wrote:
>>>>>>>>>>>> Have you tried the jtreg tests?
>>>>>>>>>>>>
>>>>>>>>>>>> The results of the jtreg tests will appear under
>>>>>>>>>>>> trunk/qa/jtreg
>>>>>>>>>>>>
>>>>>>>>>>>> jtreg constructs a web page index with detailed result
>>>>>>>>>>>> pages for
>>>>>>>>>>>> failed
>>>>>>>>>>>> tests.
>>>>>>>>>>>>
>>>>>>>>>>>> Cheers,
>>>>>>>>>>>>
>>>>>>>>>>>> Peter.
>>>>>>>>>>>>
>>>>>>>>>>>> Patricia Shanahan wrote:
>>>>>>>>>>>>> On of the simplifying steps I took to try to set up River
>>>>>>>>>>>>> development
>>>>>>>>>>>>> on a Windows box was use of a space-free path. I have since
>>>>>>>>>>>>> retested
>>>>>>>>>>>>> under "My Documents" and get QA test failures of the form:
>>>>>>>>>>>>>
>>>>>>>>>>>>> [java] com.sun.jini.qa.harness.TestException:
>>>>>>>>>>>>> [java]
>>>>>>>>>>>>> getResource(com/sun/jini/test/spec/loader/util/resources/files/file02)
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> [java]
>>>>>>>>>>>>> returned:jar:file:/C:/Documents%20and%20Settings/Administrator/My%20Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> [java] expected:jar:file:/C:/Documents and
>>>>>>>>>>>>> Settings/Administrator/My
>>>>>>>>>>>>> Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> [java] at
>>>>>>>>>>>>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.testCase(Unknown
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Source)
>>>>>>>>>>>>> [java] at
>>>>>>>>>>>>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.run(Unknown
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Source)
>>>>>>>>>>>>> [java] at com.sun.jini.qa.harness.MasterTest.doTest(Unknown
>>>>>>>>>>>>> Source)
>>>>>>>>>>>>> [java] at com.sun.jini.qa.harness.MasterTest.main(Unknown
>>>>>>>>>>>>> Source)
>>>>>>>>>>>>>
>>>>>>>>>>>>> The expected URL leaves the spaces as spaces. The returned
>>>>>>>>>>>>> URL
>>>>>>>>>>>>> has
>>>>>>>>>>>>> the
>>>>>>>>>>>>> spaces replaced, as is normal inside a URL, by %20.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Patricia
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
Re: QA tests and spaces in file names
Posted by Patricia Shanahan <pa...@acm.org>.
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6330322 is
encouraging evidence that what I am trying to do, run jtreg on Windows
XP profession SP2, can be done.
Patricia
Re: QA tests and spaces in file names
Posted by Patricia Shanahan <pa...@acm.org>.
On 7/18/2010 12:00 PM, Peter Firmstone wrote:
> Patricia Shanahan wrote:
...
>> From my selfish point of view, the move from make to ant is
>> unfortunate. As it happens, I've used make since about 1983, and I'm
>> just learning ant.
> Ironic, the motivation for ant was to reduce the barriers for attracting
> new developers. I think the barriers are, that distributed programming
> is even harder than concurrent programming, so the focus should probably
> be on making it easier to debug, your suggestions about handling failure
> (favour correctness over trying to continue) make sense to me.
I may not be typical of most new open source developers from the point
of view of education and experience. However, I do think you will find
quite a lot of people using MS-Windows, so we really need a known set-up
for my environment.
Patricia
Re: QA tests and spaces in file names
Posted by Peter Firmstone <ji...@zeus.net.au>.
Patricia Shanahan wrote:
> I tried it, and it didn't help. How should I handle jsk-policy.jar in
> the jtreg -cpa parameter? Skip it? Point to the ext directory jar file?
If jsk-policy.jar is included in your jre/lib/ext directory, leave it
out of the -cpa parameter list, it will be on the classpath for all
tests. Any classes in the jre extensions directory will be given
preference. I've seen somewhere (from memory) that Window's has two
possible places for jre extensions?
If your getting AccessException's or SecurityException's
jsk-policy.jar's visibility on the classpath will be the problem.
>
>
> Because of having tried a lot of different things, and more-or-less
> random use of JDK 1.5 and 1.6, I tried to do a new check out and
> build. Unfortunately, I don't seem to be able to get a clean build.
>
> Can you recommend a version to check out that compiles clean?
954182, my apologies, will fix it soon.
>
> Also, which JDK version should be in the path during the build?
1.6 for the build. 1.5 for the jtreg tests, although you can use 1.6 for
both, some additional tests will fail due to missing keytools, but that
might not be the case for Window's.
>
> From my selfish point of view, the move from make to ant is
> unfortunate. As it happens, I've used make since about 1983, and I'm
> just learning ant.
Ironic, the motivation for ant was to reduce the barriers for attracting
new developers. I think the barriers are, that distributed programming
is even harder than concurrent programming, so the focus should probably
be on making it easier to debug, your suggestions about handling failure
(favour correctness over trying to continue) make sense to me.
> I am less interested in getting the official mechanisms working on
> Windows than in getting some combination of scripts that will let me
> build and test.
Don't worry we'll get there, I'll have to have another crack at getting
the devel environment set up on Windows too.
>
> Patricia
>
>
> On 7/17/2010 12:51 AM, Peter Firmstone wrote:
>> Move the jsk-policy.jar to your jre/lib/ext directory
>>
>> A number of changes were made recently to make it easier to run the qa
>> and jtreg tests (at least in a Unix env), previously the qa tests were
>> run with make and the jtreg tests were run manually and generally this
>> was done so by Peter Jones from within Sun. There are also some tests
>> that rely on Sun's internal environment, we need to replicate. We have a
>> Solaris zone allocated for running a Kerberos Key server but this isn't
>> complete, we also need to set up a squid proxy.
>>
>> I made some changes to enable the jtreg tests to be run without
>> requiring jsk-policy.jar be move to jre/lib/ext/ however this might not
>> be working on windows.
>>
>
>
Re: QA tests and spaces in file names
Posted by Patricia Shanahan <pa...@acm.org>.
I tried it, and it didn't help. How should I handle jsk-policy.jar in
the jtreg -cpa parameter? Skip it? Point to the ext directory jar file?
Because of having tried a lot of different things, and more-or-less
random use of JDK 1.5 and 1.6, I tried to do a new check out and build.
Unfortunately, I don't seem to be able to get a clean build.
Can you recommend a version to check out that compiles clean?
Also, which JDK version should be in the path during the build?
From my selfish point of view, the move from make to ant is
unfortunate. As it happens, I've used make since about 1983, and I'm
just learning ant. I am less interested in getting the official
mechanisms working on Windows than in getting some combination of
scripts that will let me build and test.
Patricia
On 7/17/2010 12:51 AM, Peter Firmstone wrote:
> Move the jsk-policy.jar to your jre/lib/ext directory
>
> A number of changes were made recently to make it easier to run the qa
> and jtreg tests (at least in a Unix env), previously the qa tests were
> run with make and the jtreg tests were run manually and generally this
> was done so by Peter Jones from within Sun. There are also some tests
> that rely on Sun's internal environment, we need to replicate. We have a
> Solaris zone allocated for running a Kerberos Key server but this isn't
> complete, we also need to set up a squid proxy.
>
> I made some changes to enable the jtreg tests to be run without
> requiring jsk-policy.jar be move to jre/lib/ext/ however this might not
> be working on windows.
>
Re: QA tests and spaces in file names
Posted by Peter Firmstone <ji...@zeus.net.au>.
Move the jsk-policy.jar to your jre/lib/ext directory
A number of changes were made recently to make it easier to run the qa
and jtreg tests (at least in a Unix env), previously the qa tests were
run with make and the jtreg tests were run manually and generally this
was done so by Peter Jones from within Sun. There are also some tests
that rely on Sun's internal environment, we need to replicate. We have
a Solaris zone allocated for running a Kerberos Key server but this
isn't complete, we also need to set up a squid proxy.
I made some changes to enable the jtreg tests to be run without
requiring jsk-policy.jar be move to jre/lib/ext/ however this might not
be working on windows.
Cheers,
Peter.
Patricia Shanahan wrote:
> Got it!
>
> I now have a java.security.AccessControlException. I'll look into that
> in the morning (yawn!).
>
> Thanks,
>
> Patricia
>
>
> On 7/16/2010 12:40 AM, Peter Firmstone wrote:
>> I think it might work if you replace the path separator colon with a
>> semicolon ":" with ";"
>>
>> use -cpa;
>>
>> Peter.
>>
>> Patricia Shanahan wrote:
>>> I tried replacing the reference to the jtreg script with:
>>>
>>> java -jar c:/apache/jtreg/lib/jtreg.jar
>>>
>>> but it made no difference.
>>>
>>> Patricia
>>>
>>>
>>> On 7/15/2010 9:24 PM, Patricia Shanahan wrote:
>>>> The list of packages that are not being found is:
>>>>
>>>> com.sun.jini.action
>>>> com.sun.jini.config
>>>> com.sun.jini.jeri.internal.runtime
>>>> com.sun.jini.thread
>>>> net.jini.activation
>>>> net.jini.config
>>>> net.jini.config.AbstractConfiguration
>>>> net.jini.constraint
>>>> net.jini.constraint.BasicMethodConstraints
>>>> net.jini.core.constraint
>>>> net.jini.export
>>>> net.jini.id
>>>> net.jini.iiop
>>>> net.jini.io
>>>> net.jini.io.context
>>>> net.jini.jeri
>>>> net.jini.jeri.ServerEndpoint
>>>> net.jini.jeri.connection
>>>> net.jini.jeri.http
>>>> net.jini.jeri.kerberos
>>>> net.jini.jeri.ssl
>>>> net.jini.jeri.tcp
>>>> net.jini.jrmp
>>>> net.jini.loader
>>>> net.jini.loader.pref
>>>> net.jini.security
>>>> net.jini.security.policy
>>>> net.jini.security.proxytrust
>>>> net.jini.url.httpmd
>>>>
>>>> I know e.g. com.sun.jini.thread belongs in sun-util.jar, so I tried
>>>> copying that to the temporary library directory and adding it to the
>>>> -cpa parameter. It makes no difference. It appears the -cpa is
>>>> either in
>>>> an incorrect format for the Windows version of jtreg, or is otherwise
>>>> ineffective.
>>>>
>>>> Here is my current script:
>>>>
>>>> c:/apache/jtreg/win32/bin/jtreg "-verbose:all,nopass"
>>>> "-cpa:./qa/jtreg/JTlib-tmp/jsk.lib.jar:./qa/jtreg/JTlib-tmp/jsk-platform.jar:./qa/jtreg/JTlib-tmp/jsk-resources.jar:./qa/jtreg/JTlib-tmp/phoenix-init.jar:.jsk-policy.jar:./qa/jtreg/JTlib-tmp/sun-util.jar"
>>>>
>>>>
>>>> -jdk "c:/Program Files/Java/jdk1.6.0_20"
>>>> -Djsk.home="c:/apache/river/jtsk/trunk"
>>>> -Djava.security.debug=access,failure -Djavatest.maxOutputSize=500000
>>>> -Djtlib.tmp=./qa/jtreg/JTlib-tmp ./qa/jtreg/
>>>>
>>>>
>>>> Patricia
>>>>
>>>>
>>>>
>>>> On 7/15/2010 5:33 PM, Peter Firmstone wrote:
>>>>> Hmm, jtreg is designed to be run on all platforms supporting Java, we
>>>>> should be able to get to the bottom of the problem quickly then. I
>>>>> can
>>>>> test the command tomorrow.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Peter.
>>>>>
>>>>> Patricia Shanahan wrote:
>>>>>> The bad news is that I am still getting problems finding classes for
>>>>>> import statements. The good news is that you may have significantly
>>>>>> simplified the problem. Now I only have to learn about jtreg and its
>>>>>> parameters, not jtreg and ant and a build.xml.
>>>>>>
>>>>>> It would be a nice confirmation if you could test the command next
>>>>>> time it is convenient to do so. However, the basic issue is that I
>>>>>> have a -cpa parameter that lists .jar files that should contain the
>>>>>> packages the compiler cannot find. That gives me something to
>>>>>> investigate.
>>>>>>
>>>>>> Patricia
>>>>>>
>>>>>>
>>>>>> On 7/15/2010 1:29 AM, Peter Firmstone wrote:
>>>>>>> To run the tests manually, do the following:
>>>>>>>
>>>>>>> 1. Copy the following files to JTlib-tmp; jsk-lib.jar,
>>>>>>> jsk-platform.jar, jsk-resources.jar, phoenix-init.jar,
>>>>>>> jsk-policy.jar
>>>>>>> 2. Execute the following jtreg command from the trunk directory,
>>>>>>> change the paths to suit your environment.
>>>>>>> 3. $ jtreg -verbose:all,nopass
>>>>>>> -cpa:./qa/jtreg/JTlib-tmp/jsk.lib.jar:./qa/jtreg/JTlib-tmp/jsk-platform.jar:./qa/jtreg/JTlib-tmp/jsk-resources.jar:./qa/jtreg/JTlib-tmp/phoenix-init.jar:.jsk-policy.jar
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> -jdk /usr/jdk/jdk1.5.0_15 -Djsk.home="/opt/src/river/trunk"
>>>>>>> -Djava.security.debug=access,failure
>>>>>>> -Djavatest.maxOutputSize=500000 -Djtlib.tmp=./qa/jtreg/JTlib-tmp
>>>>>>> ./qa/jtreg/
>>>>>>>
>>>>>>> not sure if -cpa:./qa/jtreg/JTlib-tmp/* works, feel free to check.
>>>>>>> -cpa:
>>>>>>> stands for class path append.
>>>>>>>
>>>>>>> Don't worry about any test failures, this might be due to the
>>>>>>> command,
>>>>>>> we're just checking if it's an Ant problem.
>>>>>>>
>>>>>>> I can't actually test the command right now because I'm nowhere
>>>>>>> near my
>>>>>>> dev box and putty doesn't allow that many lines in a command.
>>>>>>>
>>>>>>> Cheers,
>>>>>>>
>>>>>>> Peter.
>>>>>>>
>>>>>>>
>>>>>>> Patricia Shanahan wrote:
>>>>>>>> I've just tested 1.8.0, which is before the change in question,
>>>>>>>> and it
>>>>>>>> still fails the same way. However, it is probably worth trying
>>>>>>>> using
>>>>>>>> 1.7.1 just to remove Ant version as an issue.
>>>>>>>>
>>>>>>>> Patricia
>>>>>>>>
>>>>>>>>
>>>>>>>> Peter Firmstone wrote:
>>>>>>>>> I'm using ant version 1.7.1
>>>>>>>>>
>>>>>>>>> Peter.
>>>>>>>>>
>>>>>>>>> Patricia Shanahan wrote:
>>>>>>>>>> Is anyone using the latest Ant version to run the River jtreg
>>>>>>>>>> tests?
>>>>>>>>>>
>>>>>>>>>> I'm asking because of the following comment on the Commons
>>>>>>>>>> Developers mailing list:
>>>>>>>>>>
>>>>>>>>>> "Some change in Ant has broken the property handling in the
>>>>>>>>>> Jelly/Ant
>>>>>>>>>> integration. By manually replacing jars in my local repository I
>>>>>>>>>> found
>>>>>>>>>> out that the tests pass with Ant 1.8.0 but fail with 1.8.1.
>>>>>>>>>>
>>>>>>>>>> Given that Ant's property handling has changed dramatically in
>>>>>>>>>> 1.8.x
>>>>>>>>>> and
>>>>>>>>>> Ant even marked this as a backwards incompatible change I'm
>>>>>>>>>> rather
>>>>>>>>>> surprised it still works with 1.8.0."
>>>>>>>>>>
>>>>>>>>>> I had not used Ant for a while when I started trying to get
>>>>>>>>>> involved
>>>>>>>>>> in River, so I downloaded the latest.
>>>>>>>>>>
>>>>>>>>>> Patricia
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
Re: QA tests and spaces in file names
Posted by Patricia Shanahan <pa...@acm.org>.
Got it!
I now have a java.security.AccessControlException. I'll look into that
in the morning (yawn!).
Thanks,
Patricia
On 7/16/2010 12:40 AM, Peter Firmstone wrote:
> I think it might work if you replace the path separator colon with a
> semicolon ":" with ";"
>
> use -cpa;
>
> Peter.
>
> Patricia Shanahan wrote:
>> I tried replacing the reference to the jtreg script with:
>>
>> java -jar c:/apache/jtreg/lib/jtreg.jar
>>
>> but it made no difference.
>>
>> Patricia
>>
>>
>> On 7/15/2010 9:24 PM, Patricia Shanahan wrote:
>>> The list of packages that are not being found is:
>>>
>>> com.sun.jini.action
>>> com.sun.jini.config
>>> com.sun.jini.jeri.internal.runtime
>>> com.sun.jini.thread
>>> net.jini.activation
>>> net.jini.config
>>> net.jini.config.AbstractConfiguration
>>> net.jini.constraint
>>> net.jini.constraint.BasicMethodConstraints
>>> net.jini.core.constraint
>>> net.jini.export
>>> net.jini.id
>>> net.jini.iiop
>>> net.jini.io
>>> net.jini.io.context
>>> net.jini.jeri
>>> net.jini.jeri.ServerEndpoint
>>> net.jini.jeri.connection
>>> net.jini.jeri.http
>>> net.jini.jeri.kerberos
>>> net.jini.jeri.ssl
>>> net.jini.jeri.tcp
>>> net.jini.jrmp
>>> net.jini.loader
>>> net.jini.loader.pref
>>> net.jini.security
>>> net.jini.security.policy
>>> net.jini.security.proxytrust
>>> net.jini.url.httpmd
>>>
>>> I know e.g. com.sun.jini.thread belongs in sun-util.jar, so I tried
>>> copying that to the temporary library directory and adding it to the
>>> -cpa parameter. It makes no difference. It appears the -cpa is either in
>>> an incorrect format for the Windows version of jtreg, or is otherwise
>>> ineffective.
>>>
>>> Here is my current script:
>>>
>>> c:/apache/jtreg/win32/bin/jtreg "-verbose:all,nopass"
>>> "-cpa:./qa/jtreg/JTlib-tmp/jsk.lib.jar:./qa/jtreg/JTlib-tmp/jsk-platform.jar:./qa/jtreg/JTlib-tmp/jsk-resources.jar:./qa/jtreg/JTlib-tmp/phoenix-init.jar:.jsk-policy.jar:./qa/jtreg/JTlib-tmp/sun-util.jar"
>>>
>>> -jdk "c:/Program Files/Java/jdk1.6.0_20"
>>> -Djsk.home="c:/apache/river/jtsk/trunk"
>>> -Djava.security.debug=access,failure -Djavatest.maxOutputSize=500000
>>> -Djtlib.tmp=./qa/jtreg/JTlib-tmp ./qa/jtreg/
>>>
>>>
>>> Patricia
>>>
>>>
>>>
>>> On 7/15/2010 5:33 PM, Peter Firmstone wrote:
>>>> Hmm, jtreg is designed to be run on all platforms supporting Java, we
>>>> should be able to get to the bottom of the problem quickly then. I can
>>>> test the command tomorrow.
>>>>
>>>> Cheers,
>>>>
>>>> Peter.
>>>>
>>>> Patricia Shanahan wrote:
>>>>> The bad news is that I am still getting problems finding classes for
>>>>> import statements. The good news is that you may have significantly
>>>>> simplified the problem. Now I only have to learn about jtreg and its
>>>>> parameters, not jtreg and ant and a build.xml.
>>>>>
>>>>> It would be a nice confirmation if you could test the command next
>>>>> time it is convenient to do so. However, the basic issue is that I
>>>>> have a -cpa parameter that lists .jar files that should contain the
>>>>> packages the compiler cannot find. That gives me something to
>>>>> investigate.
>>>>>
>>>>> Patricia
>>>>>
>>>>>
>>>>> On 7/15/2010 1:29 AM, Peter Firmstone wrote:
>>>>>> To run the tests manually, do the following:
>>>>>>
>>>>>> 1. Copy the following files to JTlib-tmp; jsk-lib.jar,
>>>>>> jsk-platform.jar, jsk-resources.jar, phoenix-init.jar, jsk-policy.jar
>>>>>> 2. Execute the following jtreg command from the trunk directory,
>>>>>> change the paths to suit your environment.
>>>>>> 3. $ jtreg -verbose:all,nopass
>>>>>> -cpa:./qa/jtreg/JTlib-tmp/jsk.lib.jar:./qa/jtreg/JTlib-tmp/jsk-platform.jar:./qa/jtreg/JTlib-tmp/jsk-resources.jar:./qa/jtreg/JTlib-tmp/phoenix-init.jar:.jsk-policy.jar
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> -jdk /usr/jdk/jdk1.5.0_15 -Djsk.home="/opt/src/river/trunk"
>>>>>> -Djava.security.debug=access,failure
>>>>>> -Djavatest.maxOutputSize=500000 -Djtlib.tmp=./qa/jtreg/JTlib-tmp
>>>>>> ./qa/jtreg/
>>>>>>
>>>>>> not sure if -cpa:./qa/jtreg/JTlib-tmp/* works, feel free to check.
>>>>>> -cpa:
>>>>>> stands for class path append.
>>>>>>
>>>>>> Don't worry about any test failures, this might be due to the
>>>>>> command,
>>>>>> we're just checking if it's an Ant problem.
>>>>>>
>>>>>> I can't actually test the command right now because I'm nowhere
>>>>>> near my
>>>>>> dev box and putty doesn't allow that many lines in a command.
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> Peter.
>>>>>>
>>>>>>
>>>>>> Patricia Shanahan wrote:
>>>>>>> I've just tested 1.8.0, which is before the change in question,
>>>>>>> and it
>>>>>>> still fails the same way. However, it is probably worth trying using
>>>>>>> 1.7.1 just to remove Ant version as an issue.
>>>>>>>
>>>>>>> Patricia
>>>>>>>
>>>>>>>
>>>>>>> Peter Firmstone wrote:
>>>>>>>> I'm using ant version 1.7.1
>>>>>>>>
>>>>>>>> Peter.
>>>>>>>>
>>>>>>>> Patricia Shanahan wrote:
>>>>>>>>> Is anyone using the latest Ant version to run the River jtreg
>>>>>>>>> tests?
>>>>>>>>>
>>>>>>>>> I'm asking because of the following comment on the Commons
>>>>>>>>> Developers mailing list:
>>>>>>>>>
>>>>>>>>> "Some change in Ant has broken the property handling in the
>>>>>>>>> Jelly/Ant
>>>>>>>>> integration. By manually replacing jars in my local repository I
>>>>>>>>> found
>>>>>>>>> out that the tests pass with Ant 1.8.0 but fail with 1.8.1.
>>>>>>>>>
>>>>>>>>> Given that Ant's property handling has changed dramatically in
>>>>>>>>> 1.8.x
>>>>>>>>> and
>>>>>>>>> Ant even marked this as a backwards incompatible change I'm rather
>>>>>>>>> surprised it still works with 1.8.0."
>>>>>>>>>
>>>>>>>>> I had not used Ant for a while when I started trying to get
>>>>>>>>> involved
>>>>>>>>> in River, so I downloaded the latest.
>>>>>>>>>
>>>>>>>>> Patricia
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
Re: QA tests and spaces in file names
Posted by Peter Firmstone <ji...@zeus.net.au>.
I think it might work if you replace the path separator colon with a
semicolon ":" with ";"
use -cpa;
Peter.
Patricia Shanahan wrote:
> I tried replacing the reference to the jtreg script with:
>
> java -jar c:/apache/jtreg/lib/jtreg.jar
>
> but it made no difference.
>
> Patricia
>
>
> On 7/15/2010 9:24 PM, Patricia Shanahan wrote:
>> The list of packages that are not being found is:
>>
>> com.sun.jini.action
>> com.sun.jini.config
>> com.sun.jini.jeri.internal.runtime
>> com.sun.jini.thread
>> net.jini.activation
>> net.jini.config
>> net.jini.config.AbstractConfiguration
>> net.jini.constraint
>> net.jini.constraint.BasicMethodConstraints
>> net.jini.core.constraint
>> net.jini.export
>> net.jini.id
>> net.jini.iiop
>> net.jini.io
>> net.jini.io.context
>> net.jini.jeri
>> net.jini.jeri.ServerEndpoint
>> net.jini.jeri.connection
>> net.jini.jeri.http
>> net.jini.jeri.kerberos
>> net.jini.jeri.ssl
>> net.jini.jeri.tcp
>> net.jini.jrmp
>> net.jini.loader
>> net.jini.loader.pref
>> net.jini.security
>> net.jini.security.policy
>> net.jini.security.proxytrust
>> net.jini.url.httpmd
>>
>> I know e.g. com.sun.jini.thread belongs in sun-util.jar, so I tried
>> copying that to the temporary library directory and adding it to the
>> -cpa parameter. It makes no difference. It appears the -cpa is either in
>> an incorrect format for the Windows version of jtreg, or is otherwise
>> ineffective.
>>
>> Here is my current script:
>>
>> c:/apache/jtreg/win32/bin/jtreg "-verbose:all,nopass"
>> "-cpa:./qa/jtreg/JTlib-tmp/jsk.lib.jar:./qa/jtreg/JTlib-tmp/jsk-platform.jar:./qa/jtreg/JTlib-tmp/jsk-resources.jar:./qa/jtreg/JTlib-tmp/phoenix-init.jar:.jsk-policy.jar:./qa/jtreg/JTlib-tmp/sun-util.jar"
>>
>> -jdk "c:/Program Files/Java/jdk1.6.0_20"
>> -Djsk.home="c:/apache/river/jtsk/trunk"
>> -Djava.security.debug=access,failure -Djavatest.maxOutputSize=500000
>> -Djtlib.tmp=./qa/jtreg/JTlib-tmp ./qa/jtreg/
>>
>>
>> Patricia
>>
>>
>>
>> On 7/15/2010 5:33 PM, Peter Firmstone wrote:
>>> Hmm, jtreg is designed to be run on all platforms supporting Java, we
>>> should be able to get to the bottom of the problem quickly then. I can
>>> test the command tomorrow.
>>>
>>> Cheers,
>>>
>>> Peter.
>>>
>>> Patricia Shanahan wrote:
>>>> The bad news is that I am still getting problems finding classes for
>>>> import statements. The good news is that you may have significantly
>>>> simplified the problem. Now I only have to learn about jtreg and its
>>>> parameters, not jtreg and ant and a build.xml.
>>>>
>>>> It would be a nice confirmation if you could test the command next
>>>> time it is convenient to do so. However, the basic issue is that I
>>>> have a -cpa parameter that lists .jar files that should contain the
>>>> packages the compiler cannot find. That gives me something to
>>>> investigate.
>>>>
>>>> Patricia
>>>>
>>>>
>>>> On 7/15/2010 1:29 AM, Peter Firmstone wrote:
>>>>> To run the tests manually, do the following:
>>>>>
>>>>> 1. Copy the following files to JTlib-tmp; jsk-lib.jar,
>>>>> jsk-platform.jar, jsk-resources.jar, phoenix-init.jar, jsk-policy.jar
>>>>> 2. Execute the following jtreg command from the trunk directory,
>>>>> change the paths to suit your environment.
>>>>> 3. $ jtreg -verbose:all,nopass
>>>>> -cpa:./qa/jtreg/JTlib-tmp/jsk.lib.jar:./qa/jtreg/JTlib-tmp/jsk-platform.jar:./qa/jtreg/JTlib-tmp/jsk-resources.jar:./qa/jtreg/JTlib-tmp/phoenix-init.jar:.jsk-policy.jar
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> -jdk /usr/jdk/jdk1.5.0_15 -Djsk.home="/opt/src/river/trunk"
>>>>> -Djava.security.debug=access,failure
>>>>> -Djavatest.maxOutputSize=500000 -Djtlib.tmp=./qa/jtreg/JTlib-tmp
>>>>> ./qa/jtreg/
>>>>>
>>>>> not sure if -cpa:./qa/jtreg/JTlib-tmp/* works, feel free to check.
>>>>> -cpa:
>>>>> stands for class path append.
>>>>>
>>>>> Don't worry about any test failures, this might be due to the
>>>>> command,
>>>>> we're just checking if it's an Ant problem.
>>>>>
>>>>> I can't actually test the command right now because I'm nowhere
>>>>> near my
>>>>> dev box and putty doesn't allow that many lines in a command.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Peter.
>>>>>
>>>>>
>>>>> Patricia Shanahan wrote:
>>>>>> I've just tested 1.8.0, which is before the change in question,
>>>>>> and it
>>>>>> still fails the same way. However, it is probably worth trying using
>>>>>> 1.7.1 just to remove Ant version as an issue.
>>>>>>
>>>>>> Patricia
>>>>>>
>>>>>>
>>>>>> Peter Firmstone wrote:
>>>>>>> I'm using ant version 1.7.1
>>>>>>>
>>>>>>> Peter.
>>>>>>>
>>>>>>> Patricia Shanahan wrote:
>>>>>>>> Is anyone using the latest Ant version to run the River jtreg
>>>>>>>> tests?
>>>>>>>>
>>>>>>>> I'm asking because of the following comment on the Commons
>>>>>>>> Developers mailing list:
>>>>>>>>
>>>>>>>> "Some change in Ant has broken the property handling in the
>>>>>>>> Jelly/Ant
>>>>>>>> integration. By manually replacing jars in my local repository I
>>>>>>>> found
>>>>>>>> out that the tests pass with Ant 1.8.0 but fail with 1.8.1.
>>>>>>>>
>>>>>>>> Given that Ant's property handling has changed dramatically in
>>>>>>>> 1.8.x
>>>>>>>> and
>>>>>>>> Ant even marked this as a backwards incompatible change I'm rather
>>>>>>>> surprised it still works with 1.8.0."
>>>>>>>>
>>>>>>>> I had not used Ant for a while when I started trying to get
>>>>>>>> involved
>>>>>>>> in River, so I downloaded the latest.
>>>>>>>>
>>>>>>>> Patricia
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
Re: QA tests and spaces in file names
Posted by Patricia Shanahan <pa...@acm.org>.
I tried replacing the reference to the jtreg script with:
java -jar c:/apache/jtreg/lib/jtreg.jar
but it made no difference.
Patricia
On 7/15/2010 9:24 PM, Patricia Shanahan wrote:
> The list of packages that are not being found is:
>
> com.sun.jini.action
> com.sun.jini.config
> com.sun.jini.jeri.internal.runtime
> com.sun.jini.thread
> net.jini.activation
> net.jini.config
> net.jini.config.AbstractConfiguration
> net.jini.constraint
> net.jini.constraint.BasicMethodConstraints
> net.jini.core.constraint
> net.jini.export
> net.jini.id
> net.jini.iiop
> net.jini.io
> net.jini.io.context
> net.jini.jeri
> net.jini.jeri.ServerEndpoint
> net.jini.jeri.connection
> net.jini.jeri.http
> net.jini.jeri.kerberos
> net.jini.jeri.ssl
> net.jini.jeri.tcp
> net.jini.jrmp
> net.jini.loader
> net.jini.loader.pref
> net.jini.security
> net.jini.security.policy
> net.jini.security.proxytrust
> net.jini.url.httpmd
>
> I know e.g. com.sun.jini.thread belongs in sun-util.jar, so I tried
> copying that to the temporary library directory and adding it to the
> -cpa parameter. It makes no difference. It appears the -cpa is either in
> an incorrect format for the Windows version of jtreg, or is otherwise
> ineffective.
>
> Here is my current script:
>
> c:/apache/jtreg/win32/bin/jtreg "-verbose:all,nopass"
> "-cpa:./qa/jtreg/JTlib-tmp/jsk.lib.jar:./qa/jtreg/JTlib-tmp/jsk-platform.jar:./qa/jtreg/JTlib-tmp/jsk-resources.jar:./qa/jtreg/JTlib-tmp/phoenix-init.jar:.jsk-policy.jar:./qa/jtreg/JTlib-tmp/sun-util.jar"
> -jdk "c:/Program Files/Java/jdk1.6.0_20"
> -Djsk.home="c:/apache/river/jtsk/trunk"
> -Djava.security.debug=access,failure -Djavatest.maxOutputSize=500000
> -Djtlib.tmp=./qa/jtreg/JTlib-tmp ./qa/jtreg/
>
>
> Patricia
>
>
>
> On 7/15/2010 5:33 PM, Peter Firmstone wrote:
>> Hmm, jtreg is designed to be run on all platforms supporting Java, we
>> should be able to get to the bottom of the problem quickly then. I can
>> test the command tomorrow.
>>
>> Cheers,
>>
>> Peter.
>>
>> Patricia Shanahan wrote:
>>> The bad news is that I am still getting problems finding classes for
>>> import statements. The good news is that you may have significantly
>>> simplified the problem. Now I only have to learn about jtreg and its
>>> parameters, not jtreg and ant and a build.xml.
>>>
>>> It would be a nice confirmation if you could test the command next
>>> time it is convenient to do so. However, the basic issue is that I
>>> have a -cpa parameter that lists .jar files that should contain the
>>> packages the compiler cannot find. That gives me something to
>>> investigate.
>>>
>>> Patricia
>>>
>>>
>>> On 7/15/2010 1:29 AM, Peter Firmstone wrote:
>>>> To run the tests manually, do the following:
>>>>
>>>> 1. Copy the following files to JTlib-tmp; jsk-lib.jar,
>>>> jsk-platform.jar, jsk-resources.jar, phoenix-init.jar, jsk-policy.jar
>>>> 2. Execute the following jtreg command from the trunk directory,
>>>> change the paths to suit your environment.
>>>> 3. $ jtreg -verbose:all,nopass
>>>> -cpa:./qa/jtreg/JTlib-tmp/jsk.lib.jar:./qa/jtreg/JTlib-tmp/jsk-platform.jar:./qa/jtreg/JTlib-tmp/jsk-resources.jar:./qa/jtreg/JTlib-tmp/phoenix-init.jar:.jsk-policy.jar
>>>>
>>>>
>>>>
>>>> -jdk /usr/jdk/jdk1.5.0_15 -Djsk.home="/opt/src/river/trunk"
>>>> -Djava.security.debug=access,failure
>>>> -Djavatest.maxOutputSize=500000 -Djtlib.tmp=./qa/jtreg/JTlib-tmp
>>>> ./qa/jtreg/
>>>>
>>>> not sure if -cpa:./qa/jtreg/JTlib-tmp/* works, feel free to check.
>>>> -cpa:
>>>> stands for class path append.
>>>>
>>>> Don't worry about any test failures, this might be due to the command,
>>>> we're just checking if it's an Ant problem.
>>>>
>>>> I can't actually test the command right now because I'm nowhere near my
>>>> dev box and putty doesn't allow that many lines in a command.
>>>>
>>>> Cheers,
>>>>
>>>> Peter.
>>>>
>>>>
>>>> Patricia Shanahan wrote:
>>>>> I've just tested 1.8.0, which is before the change in question, and it
>>>>> still fails the same way. However, it is probably worth trying using
>>>>> 1.7.1 just to remove Ant version as an issue.
>>>>>
>>>>> Patricia
>>>>>
>>>>>
>>>>> Peter Firmstone wrote:
>>>>>> I'm using ant version 1.7.1
>>>>>>
>>>>>> Peter.
>>>>>>
>>>>>> Patricia Shanahan wrote:
>>>>>>> Is anyone using the latest Ant version to run the River jtreg tests?
>>>>>>>
>>>>>>> I'm asking because of the following comment on the Commons
>>>>>>> Developers mailing list:
>>>>>>>
>>>>>>> "Some change in Ant has broken the property handling in the
>>>>>>> Jelly/Ant
>>>>>>> integration. By manually replacing jars in my local repository I
>>>>>>> found
>>>>>>> out that the tests pass with Ant 1.8.0 but fail with 1.8.1.
>>>>>>>
>>>>>>> Given that Ant's property handling has changed dramatically in 1.8.x
>>>>>>> and
>>>>>>> Ant even marked this as a backwards incompatible change I'm rather
>>>>>>> surprised it still works with 1.8.0."
>>>>>>>
>>>>>>> I had not used Ant for a while when I started trying to get involved
>>>>>>> in River, so I downloaded the latest.
>>>>>>>
>>>>>>> Patricia
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
Re: QA tests and spaces in file names
Posted by Patricia Shanahan <pa...@acm.org>.
The list of packages that are not being found is:
com.sun.jini.action
com.sun.jini.config
com.sun.jini.jeri.internal.runtime
com.sun.jini.thread
net.jini.activation
net.jini.config
net.jini.config.AbstractConfiguration
net.jini.constraint
net.jini.constraint.BasicMethodConstraints
net.jini.core.constraint
net.jini.export
net.jini.id
net.jini.iiop
net.jini.io
net.jini.io.context
net.jini.jeri
net.jini.jeri.ServerEndpoint
net.jini.jeri.connection
net.jini.jeri.http
net.jini.jeri.kerberos
net.jini.jeri.ssl
net.jini.jeri.tcp
net.jini.jrmp
net.jini.loader
net.jini.loader.pref
net.jini.security
net.jini.security.policy
net.jini.security.proxytrust
net.jini.url.httpmd
I know e.g. com.sun.jini.thread belongs in sun-util.jar, so I tried
copying that to the temporary library directory and adding it to the
-cpa parameter. It makes no difference. It appears the -cpa is either in
an incorrect format for the Windows version of jtreg, or is otherwise
ineffective.
Here is my current script:
c:/apache/jtreg/win32/bin/jtreg "-verbose:all,nopass"
"-cpa:./qa/jtreg/JTlib-tmp/jsk.lib.jar:./qa/jtreg/JTlib-tmp/jsk-platform.jar:./qa/jtreg/JTlib-tmp/jsk-resources.jar:./qa/jtreg/JTlib-tmp/phoenix-init.jar:.jsk-policy.jar:./qa/jtreg/JTlib-tmp/sun-util.jar"
-jdk "c:/Program Files/Java/jdk1.6.0_20"
-Djsk.home="c:/apache/river/jtsk/trunk"
-Djava.security.debug=access,failure -Djavatest.maxOutputSize=500000
-Djtlib.tmp=./qa/jtreg/JTlib-tmp ./qa/jtreg/
Patricia
On 7/15/2010 5:33 PM, Peter Firmstone wrote:
> Hmm, jtreg is designed to be run on all platforms supporting Java, we
> should be able to get to the bottom of the problem quickly then. I can
> test the command tomorrow.
>
> Cheers,
>
> Peter.
>
> Patricia Shanahan wrote:
>> The bad news is that I am still getting problems finding classes for
>> import statements. The good news is that you may have significantly
>> simplified the problem. Now I only have to learn about jtreg and its
>> parameters, not jtreg and ant and a build.xml.
>>
>> It would be a nice confirmation if you could test the command next
>> time it is convenient to do so. However, the basic issue is that I
>> have a -cpa parameter that lists .jar files that should contain the
>> packages the compiler cannot find. That gives me something to
>> investigate.
>>
>> Patricia
>>
>>
>> On 7/15/2010 1:29 AM, Peter Firmstone wrote:
>>> To run the tests manually, do the following:
>>>
>>> 1. Copy the following files to JTlib-tmp; jsk-lib.jar,
>>> jsk-platform.jar, jsk-resources.jar, phoenix-init.jar, jsk-policy.jar
>>> 2. Execute the following jtreg command from the trunk directory,
>>> change the paths to suit your environment.
>>> 3. $ jtreg -verbose:all,nopass
>>> -cpa:./qa/jtreg/JTlib-tmp/jsk.lib.jar:./qa/jtreg/JTlib-tmp/jsk-platform.jar:./qa/jtreg/JTlib-tmp/jsk-resources.jar:./qa/jtreg/JTlib-tmp/phoenix-init.jar:.jsk-policy.jar
>>>
>>>
>>> -jdk /usr/jdk/jdk1.5.0_15 -Djsk.home="/opt/src/river/trunk"
>>> -Djava.security.debug=access,failure
>>> -Djavatest.maxOutputSize=500000 -Djtlib.tmp=./qa/jtreg/JTlib-tmp
>>> ./qa/jtreg/
>>>
>>> not sure if -cpa:./qa/jtreg/JTlib-tmp/* works, feel free to check. -cpa:
>>> stands for class path append.
>>>
>>> Don't worry about any test failures, this might be due to the command,
>>> we're just checking if it's an Ant problem.
>>>
>>> I can't actually test the command right now because I'm nowhere near my
>>> dev box and putty doesn't allow that many lines in a command.
>>>
>>> Cheers,
>>>
>>> Peter.
>>>
>>>
>>> Patricia Shanahan wrote:
>>>> I've just tested 1.8.0, which is before the change in question, and it
>>>> still fails the same way. However, it is probably worth trying using
>>>> 1.7.1 just to remove Ant version as an issue.
>>>>
>>>> Patricia
>>>>
>>>>
>>>> Peter Firmstone wrote:
>>>>> I'm using ant version 1.7.1
>>>>>
>>>>> Peter.
>>>>>
>>>>> Patricia Shanahan wrote:
>>>>>> Is anyone using the latest Ant version to run the River jtreg tests?
>>>>>>
>>>>>> I'm asking because of the following comment on the Commons
>>>>>> Developers mailing list:
>>>>>>
>>>>>> "Some change in Ant has broken the property handling in the Jelly/Ant
>>>>>> integration. By manually replacing jars in my local repository I
>>>>>> found
>>>>>> out that the tests pass with Ant 1.8.0 but fail with 1.8.1.
>>>>>>
>>>>>> Given that Ant's property handling has changed dramatically in 1.8.x
>>>>>> and
>>>>>> Ant even marked this as a backwards incompatible change I'm rather
>>>>>> surprised it still works with 1.8.0."
>>>>>>
>>>>>> I had not used Ant for a while when I started trying to get involved
>>>>>> in River, so I downloaded the latest.
>>>>>>
>>>>>> Patricia
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>
>
Re: QA tests and spaces in file names
Posted by Peter Firmstone <ji...@zeus.net.au>.
Hmm, jtreg is designed to be run on all platforms supporting Java, we
should be able to get to the bottom of the problem quickly then. I can
test the command tomorrow.
Cheers,
Peter.
Patricia Shanahan wrote:
> The bad news is that I am still getting problems finding classes for
> import statements. The good news is that you may have significantly
> simplified the problem. Now I only have to learn about jtreg and its
> parameters, not jtreg and ant and a build.xml.
>
> It would be a nice confirmation if you could test the command next
> time it is convenient to do so. However, the basic issue is that I
> have a -cpa parameter that lists .jar files that should contain the
> packages the compiler cannot find. That gives me something to
> investigate.
>
> Patricia
>
>
> On 7/15/2010 1:29 AM, Peter Firmstone wrote:
>> To run the tests manually, do the following:
>>
>> 1. Copy the following files to JTlib-tmp; jsk-lib.jar,
>> jsk-platform.jar, jsk-resources.jar, phoenix-init.jar, jsk-policy.jar
>> 2. Execute the following jtreg command from the trunk directory,
>> change the paths to suit your environment.
>> 3. $ jtreg -verbose:all,nopass
>> -cpa:./qa/jtreg/JTlib-tmp/jsk.lib.jar:./qa/jtreg/JTlib-tmp/jsk-platform.jar:./qa/jtreg/JTlib-tmp/jsk-resources.jar:./qa/jtreg/JTlib-tmp/phoenix-init.jar:.jsk-policy.jar
>>
>>
>> -jdk /usr/jdk/jdk1.5.0_15 -Djsk.home="/opt/src/river/trunk"
>> -Djava.security.debug=access,failure
>> -Djavatest.maxOutputSize=500000 -Djtlib.tmp=./qa/jtreg/JTlib-tmp
>> ./qa/jtreg/
>>
>> not sure if -cpa:./qa/jtreg/JTlib-tmp/* works, feel free to check. -cpa:
>> stands for class path append.
>>
>> Don't worry about any test failures, this might be due to the command,
>> we're just checking if it's an Ant problem.
>>
>> I can't actually test the command right now because I'm nowhere near my
>> dev box and putty doesn't allow that many lines in a command.
>>
>> Cheers,
>>
>> Peter.
>>
>>
>> Patricia Shanahan wrote:
>>> I've just tested 1.8.0, which is before the change in question, and it
>>> still fails the same way. However, it is probably worth trying using
>>> 1.7.1 just to remove Ant version as an issue.
>>>
>>> Patricia
>>>
>>>
>>> Peter Firmstone wrote:
>>>> I'm using ant version 1.7.1
>>>>
>>>> Peter.
>>>>
>>>> Patricia Shanahan wrote:
>>>>> Is anyone using the latest Ant version to run the River jtreg tests?
>>>>>
>>>>> I'm asking because of the following comment on the Commons
>>>>> Developers mailing list:
>>>>>
>>>>> "Some change in Ant has broken the property handling in the Jelly/Ant
>>>>> integration. By manually replacing jars in my local repository I
>>>>> found
>>>>> out that the tests pass with Ant 1.8.0 but fail with 1.8.1.
>>>>>
>>>>> Given that Ant's property handling has changed dramatically in 1.8.x
>>>>> and
>>>>> Ant even marked this as a backwards incompatible change I'm rather
>>>>> surprised it still works with 1.8.0."
>>>>>
>>>>> I had not used Ant for a while when I started trying to get involved
>>>>> in River, so I downloaded the latest.
>>>>>
>>>>> Patricia
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>>
>
>
Re: QA tests and spaces in file names
Posted by Patricia Shanahan <pa...@acm.org>.
The bad news is that I am still getting problems finding classes for
import statements. The good news is that you may have significantly
simplified the problem. Now I only have to learn about jtreg and its
parameters, not jtreg and ant and a build.xml.
It would be a nice confirmation if you could test the command next time
it is convenient to do so. However, the basic issue is that I have a
-cpa parameter that lists .jar files that should contain the packages
the compiler cannot find. That gives me something to investigate.
Patricia
On 7/15/2010 1:29 AM, Peter Firmstone wrote:
> To run the tests manually, do the following:
>
> 1. Copy the following files to JTlib-tmp; jsk-lib.jar,
> jsk-platform.jar, jsk-resources.jar, phoenix-init.jar, jsk-policy.jar
> 2. Execute the following jtreg command from the trunk directory,
> change the paths to suit your environment.
> 3. $ jtreg -verbose:all,nopass
> -cpa:./qa/jtreg/JTlib-tmp/jsk.lib.jar:./qa/jtreg/JTlib-tmp/jsk-platform.jar:./qa/jtreg/JTlib-tmp/jsk-resources.jar:./qa/jtreg/JTlib-tmp/phoenix-init.jar:.jsk-policy.jar
>
> -jdk /usr/jdk/jdk1.5.0_15 -Djsk.home="/opt/src/river/trunk"
> -Djava.security.debug=access,failure
> -Djavatest.maxOutputSize=500000 -Djtlib.tmp=./qa/jtreg/JTlib-tmp
> ./qa/jtreg/
>
> not sure if -cpa:./qa/jtreg/JTlib-tmp/* works, feel free to check. -cpa:
> stands for class path append.
>
> Don't worry about any test failures, this might be due to the command,
> we're just checking if it's an Ant problem.
>
> I can't actually test the command right now because I'm nowhere near my
> dev box and putty doesn't allow that many lines in a command.
>
> Cheers,
>
> Peter.
>
>
> Patricia Shanahan wrote:
>> I've just tested 1.8.0, which is before the change in question, and it
>> still fails the same way. However, it is probably worth trying using
>> 1.7.1 just to remove Ant version as an issue.
>>
>> Patricia
>>
>>
>> Peter Firmstone wrote:
>>> I'm using ant version 1.7.1
>>>
>>> Peter.
>>>
>>> Patricia Shanahan wrote:
>>>> Is anyone using the latest Ant version to run the River jtreg tests?
>>>>
>>>> I'm asking because of the following comment on the Commons
>>>> Developers mailing list:
>>>>
>>>> "Some change in Ant has broken the property handling in the Jelly/Ant
>>>> integration. By manually replacing jars in my local repository I found
>>>> out that the tests pass with Ant 1.8.0 but fail with 1.8.1.
>>>>
>>>> Given that Ant's property handling has changed dramatically in 1.8.x
>>>> and
>>>> Ant even marked this as a backwards incompatible change I'm rather
>>>> surprised it still works with 1.8.0."
>>>>
>>>> I had not used Ant for a while when I started trying to get involved
>>>> in River, so I downloaded the latest.
>>>>
>>>> Patricia
>>>>
>>>
>>>
>>
>>
>
>
>
Re: QA tests and spaces in file names
Posted by Peter Firmstone <ji...@zeus.net.au>.
To run the tests manually, do the following:
1. Copy the following files to JTlib-tmp; jsk-lib.jar,
jsk-platform.jar, jsk-resources.jar, phoenix-init.jar, jsk-policy.jar
2. Execute the following jtreg command from the trunk directory,
change the paths to suit your environment.
3. $ jtreg -verbose:all,nopass
-cpa:./qa/jtreg/JTlib-tmp/jsk.lib.jar:./qa/jtreg/JTlib-tmp/jsk-platform.jar:./qa/jtreg/JTlib-tmp/jsk-resources.jar:./qa/jtreg/JTlib-tmp/phoenix-init.jar:.jsk-policy.jar
-jdk /usr/jdk/jdk1.5.0_15 -Djsk.home="/opt/src/river/trunk"
-Djava.security.debug=access,failure
-Djavatest.maxOutputSize=500000 -Djtlib.tmp=./qa/jtreg/JTlib-tmp
./qa/jtreg/
not sure if -cpa:./qa/jtreg/JTlib-tmp/* works, feel free to check.
-cpa: stands for class path append.
Don't worry about any test failures, this might be due to the command,
we're just checking if it's an Ant problem.
I can't actually test the command right now because I'm nowhere near my
dev box and putty doesn't allow that many lines in a command.
Cheers,
Peter.
Patricia Shanahan wrote:
> I've just tested 1.8.0, which is before the change in question, and it
> still fails the same way. However, it is probably worth trying using
> 1.7.1 just to remove Ant version as an issue.
>
> Patricia
>
>
> Peter Firmstone wrote:
>> I'm using ant version 1.7.1
>>
>> Peter.
>>
>> Patricia Shanahan wrote:
>>> Is anyone using the latest Ant version to run the River jtreg tests?
>>>
>>> I'm asking because of the following comment on the Commons
>>> Developers mailing list:
>>>
>>> "Some change in Ant has broken the property handling in the Jelly/Ant
>>> integration. By manually replacing jars in my local repository I found
>>> out that the tests pass with Ant 1.8.0 but fail with 1.8.1.
>>>
>>> Given that Ant's property handling has changed dramatically in 1.8.x
>>> and
>>> Ant even marked this as a backwards incompatible change I'm rather
>>> surprised it still works with 1.8.0."
>>>
>>> I had not used Ant for a while when I started trying to get involved
>>> in River, so I downloaded the latest.
>>>
>>> Patricia
>>>
>>
>>
>
>
Re: QA tests and spaces in file names
Posted by Patricia Shanahan <pa...@acm.org>.
I've just tested 1.8.0, which is before the change in question, and it
still fails the same way. However, it is probably worth trying using
1.7.1 just to remove Ant version as an issue.
Patricia
Peter Firmstone wrote:
> I'm using ant version 1.7.1
>
> Peter.
>
> Patricia Shanahan wrote:
>> Is anyone using the latest Ant version to run the River jtreg tests?
>>
>> I'm asking because of the following comment on the Commons Developers
>> mailing list:
>>
>> "Some change in Ant has broken the property handling in the Jelly/Ant
>> integration. By manually replacing jars in my local repository I found
>> out that the tests pass with Ant 1.8.0 but fail with 1.8.1.
>>
>> Given that Ant's property handling has changed dramatically in 1.8.x and
>> Ant even marked this as a backwards incompatible change I'm rather
>> surprised it still works with 1.8.0."
>>
>> I had not used Ant for a while when I started trying to get involved
>> in River, so I downloaded the latest.
>>
>> Patricia
>>
>
>
Re: QA tests and spaces in file names
Posted by Peter Firmstone <ji...@zeus.net.au>.
I'm using ant version 1.7.1
Peter.
Patricia Shanahan wrote:
> Is anyone using the latest Ant version to run the River jtreg tests?
>
> I'm asking because of the following comment on the Commons Developers
> mailing list:
>
> "Some change in Ant has broken the property handling in the Jelly/Ant
> integration. By manually replacing jars in my local repository I found
> out that the tests pass with Ant 1.8.0 but fail with 1.8.1.
>
> Given that Ant's property handling has changed dramatically in 1.8.x and
> Ant even marked this as a backwards incompatible change I'm rather
> surprised it still works with 1.8.0."
>
> I had not used Ant for a while when I started trying to get involved
> in River, so I downloaded the latest.
>
> Patricia
>
Re: QA tests and spaces in file names
Posted by Patricia Shanahan <pa...@acm.org>.
Is anyone using the latest Ant version to run the River jtreg tests?
I'm asking because of the following comment on the Commons Developers
mailing list:
"Some change in Ant has broken the property handling in the Jelly/Ant
integration. By manually replacing jars in my local repository I found
out that the tests pass with Ant 1.8.0 but fail with 1.8.1.
Given that Ant's property handling has changed dramatically in 1.8.x and
Ant even marked this as a backwards incompatible change I'm rather
surprised it still works with 1.8.0."
I had not used Ant for a while when I started trying to get involved in
River, so I downloaded the latest.
Patricia
Peter Firmstone wrote:
> river.jar defines the directory is where the most of the jar files
> created by the build process live. This doesn't affect jtreg directly
> however, the files needed for the jtreg tests are moved into the
> JTlib-tmp directory.
>
> This is defined by the jtlib.tmp property.
>
> I wonder if there's a problem with the hyphen or mixed case for the
> JTlib-tmp directory?
>
> It's a long shot but that's the directory where the missing class files
> originate, otherwise it might have something to do with the -cpa: option.
>
> Cheers,
>
> Peter.
>
>
>
> Patricia Shanahan wrote:
>> Do you know anything about "river.jars"? It seems to be used in
>> setting classpathref, and my errors do look very classpathish.
>>
...
Re: QA tests and spaces in file names
Posted by Peter Firmstone <ji...@zeus.net.au>.
river.jar defines the directory is where the most of the jar files
created by the build process live. This doesn't affect jtreg directly
however, the files needed for the jtreg tests are moved into the
JTlib-tmp directory.
This is defined by the jtlib.tmp property.
I wonder if there's a problem with the hyphen or mixed case for the
JTlib-tmp directory?
It's a long shot but that's the directory where the missing class files
originate, otherwise it might have something to do with the -cpa: option.
Cheers,
Peter.
Patricia Shanahan wrote:
> Do you know anything about "river.jars"? It seems to be used in
> setting classpathref, and my errors do look very classpathish.
>
> Patricia
>
>
> On 7/13/2010 1:43 AM, Peter Firmstone wrote:
>> My comments here might also be of assistance:
>>
>> https://issues.apache.org/jira/browse/RIVER-319
>>
>> Patricia Shanahan wrote:
>>> Correct. I did try using only "/" as path separator, and it still
>>> failed. Here is my latest build.properties:
>>>
>>> bash-3.2$ pwd
>>> /cygdrive/c/apache/river/jtsk/trunk/qa
>>> bash-3.2$ cat build.properties
>>> river.home=c:/apache/river/jtsk/trunk
>>> jtreg.home=c:/apache/jtreg
>>> jtreg.dir=C:/apache/river/jtsk/trunk/qa/jtreg
>>> jdk1.5.home=C:/Program Files (x86)/Java/jdk1.5.0_22
>>>
>>> The output is in http://www.patriciashanahan.com/apache/myJTREGLog.txt
>>>
>>> Maybe somebody could make available to me the output from a correct
>>> regression test? Part of my problem is that, being unfamiliar with
>>> River, the Apache development flow in general, and JTreg in
>>> particular, I don't know what output to expect.
>>>
>>> The problems look to me rather like a compile-time classpath problem -
>>> files are found if the scripts are looking for them directly, but the
>>> compiler cannot find packages for import statements.
>>>
>>> Thanks for any suggestions,
>>>
>>> Patricia
>>>
>>>
>>> On 7/12/2010 7:57 AM, Gregg Wonderly wrote:
>>>> As a general rule, there is no reason to use '\' in java paths that
>>>> are
>>>> passed into any class that uses the path inside of the JVM. Only when
>>>> you use Runtime.exec() et.al. do you need to worry about '/' vs '\'.
>>>> Windows, a long time ago, recognized '/' internally as a path
>>>> separator,
>>>> because only the 'shell' was dealing with '/' as an option delimiter.
>>>>
>>>> It makes life a lot easier to just use '/' for java.lang.File paths
>>>> and
>>>> in particular, it simplifies property file and other text usage where
>>>> '\' is interpreted by the class as a special character.
>>>>
>>>> Gregg Wonderly
>>>>
>>>> Patricia Shanahan wrote:
>>>>> Promising. I got error messages at first because I forgot to
>>>>> double up
>>>>> the "/" characters, so it was paying attention to the jtreg.dir line.
>>>>> Once I fixed that it went to:
>>>>>
>>>>> Buildfile: C:\apache\river\jtsk\trunk\qa\build.xml
>>>>>
>>>>> jtreg:
>>>>> [mkdir] Created dir: C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
>>>>> [move] Moving 4 files to C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
>>>>> [move] Moving 1 file to C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
>>>>> [move] Moving 1 file to C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
>>>>>
>>>>> BUILD FAILED
>>>>> C:\apache\river\jtsk\trunk\qa\build.xml:156: Cannot determine test
>>>>> suite from test (is TEST.ROOT missing?):
>>>>> C:\apache\river\jtsk\qa\jtreg\JTlib-tmp\concurrent-policy-util.jar
>>>>>
>>>>> Total time: 1 second
>>>>>
>>>>>
>>>>> What do you think it would like for TEST.ROOT?
>>>>>
>>>>>
>>>>> On 7/9/2010 11:55 PM, Peter Firmstone wrote:
>>>>>> Try adding this to your build.properties file:
>>>>>>
>>>>>> jtreg.dir=C:\apache\river\jtsk\qa\jtreg
>>>>>>
>>>>>> Peter.
>>>>>>
>>>>>> Patricia Shanahan wrote:
>>>>>>> Yes, I ran it in the root directory.
>>>>>>>
>>>>>>>
>>>>>>> Patricia
>>>>>>>
>>>>>>> On Jul 9, 2010, at 21:35, Peter Firmstone <ji...@zeus.net.au> wrote:
>>>>>>>
>>>>>>>> It appears as though it can't see the jar archives in the
>>>>>>>> directory:
>>>>>>>>
>>>>>>>> C;\apache\river\jtsk\trunk\lib\
>>>>>>>>
>>>>>>>> The missing class is from jsk-platform.jar
>>>>>>>>
>>>>>>>> Did you run ant all.build first?
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>>
>>>>>>>> Peter.
>>>>>>>>
>>>>>>>> Patricia Shanahan wrote:
>>>>>>>>> Sure:
>>>>>>>>>
>>>>>>>>> http://www.patriciashanahan.com/apache/myJTREGLog.txt
>>>>>>>>>
>>>>>>>>> Patricia
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 7/9/2010 7:59 PM, Peter Firmstone wrote:
>>>>>>>>>> Can you dump the output to a text file and submit it?
>>>>>>>>>>
>>>>>>>>>> Peter.
>>>>>>>>>>
>>>>>>>>>> Patricia Shanahan wrote:
>>>>>>>>>>> I tried that. It didn't seem to make any difference.
>>>>>>>>>>>
>>>>>>>>>>> Patricia
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On 7/9/2010 4:48 PM, Peter Firmstone wrote:
>>>>>>>>>>>> Try copying your existing build.properties file to the qa
>>>>>>>>>>>> directory,
>>>>>>>>>>>> just for now.
>>>>>>>>>>>>
>>>>>>>>>>>> Then try the jtreg tests again too.
>>>>>>>>>>>>
>>>>>>>>>>>> Cheers,
>>>>>>>>>>>>
>>>>>>>>>>>> Peter.
>>>>>>>>>>>>
>>>>>>>>>>>> Patricia Shanahan wrote:
>>>>>>>>>>>>> The problem seems to be a classpath issue when compiling the
>>>>>>>>>>>>> tests. I
>>>>>>>>>>>>> get messages of the form:
>>>>>>>>>>>>>
>>>>>>>>>>>>> C:\\apache\\river\\jtsk\\trunk\\qa\\jtreg\\com\\sun\\jini\\action\\catchSecurityException\\CatchSecurityException.java:30:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> package com.sun.jini.action does not exist
>>>>>>>>>>>>> import com.sun.jini.action.GetBooleanAction;
>>>>>>>>>>>>>
>>>>>>>>>>>>> Do I need another build.properties file in the qa directory?
>>>>>>>>>>>>> If so,
>>>>>>>>>>>>> what should it contain?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Patricia
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On 7/9/2010 4:04 AM, Peter Firmstone wrote:
>>>>>>>>>>>>>> Have you tried the jtreg tests?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> The results of the jtreg tests will appear under
>>>>>>>>>>>>>> trunk/qa/jtreg
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> jtreg constructs a web page index with detailed result
>>>>>>>>>>>>>> pages for
>>>>>>>>>>>>>> failed
>>>>>>>>>>>>>> tests.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Cheers,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Peter.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Patricia Shanahan wrote:
>>>>>>>>>>>>>>> On of the simplifying steps I took to try to set up River
>>>>>>>>>>>>>>> development
>>>>>>>>>>>>>>> on a Windows box was use of a space-free path. I have since
>>>>>>>>>>>>>>> retested
>>>>>>>>>>>>>>> under "My Documents" and get QA test failures of the form:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> [java] com.sun.jini.qa.harness.TestException:
>>>>>>>>>>>>>>> [java]
>>>>>>>>>>>>>>> getResource(com/sun/jini/test/spec/loader/util/resources/files/file02)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> [java]
>>>>>>>>>>>>>>> returned:jar:file:/C:/Documents%20and%20Settings/Administrator/My%20Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> [java] expected:jar:file:/C:/Documents and
>>>>>>>>>>>>>>> Settings/Administrator/My
>>>>>>>>>>>>>>> Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> [java] at
>>>>>>>>>>>>>>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.testCase(Unknown
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Source)
>>>>>>>>>>>>>>> [java] at
>>>>>>>>>>>>>>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.run(Unknown
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Source)
>>>>>>>>>>>>>>> [java] at com.sun.jini.qa.harness.MasterTest.doTest(Unknown
>>>>>>>>>>>>>>> Source)
>>>>>>>>>>>>>>> [java] at com.sun.jini.qa.harness.MasterTest.main(Unknown
>>>>>>>>>>>>>>> Source)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> The expected URL leaves the spaces as spaces. The returned
>>>>>>>>>>>>>>> URL
>>>>>>>>>>>>>>> has
>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>> spaces replaced, as is normal inside a URL, by %20.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Patricia
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
Re: QA tests and spaces in file names
Posted by Patricia Shanahan <pa...@acm.org>.
Do you know anything about "river.jars"? It seems to be used in setting
classpathref, and my errors do look very classpathish.
Patricia
On 7/13/2010 1:43 AM, Peter Firmstone wrote:
> My comments here might also be of assistance:
>
> https://issues.apache.org/jira/browse/RIVER-319
>
> Patricia Shanahan wrote:
>> Correct. I did try using only "/" as path separator, and it still
>> failed. Here is my latest build.properties:
>>
>> bash-3.2$ pwd
>> /cygdrive/c/apache/river/jtsk/trunk/qa
>> bash-3.2$ cat build.properties
>> river.home=c:/apache/river/jtsk/trunk
>> jtreg.home=c:/apache/jtreg
>> jtreg.dir=C:/apache/river/jtsk/trunk/qa/jtreg
>> jdk1.5.home=C:/Program Files (x86)/Java/jdk1.5.0_22
>>
>> The output is in http://www.patriciashanahan.com/apache/myJTREGLog.txt
>>
>> Maybe somebody could make available to me the output from a correct
>> regression test? Part of my problem is that, being unfamiliar with
>> River, the Apache development flow in general, and JTreg in
>> particular, I don't know what output to expect.
>>
>> The problems look to me rather like a compile-time classpath problem -
>> files are found if the scripts are looking for them directly, but the
>> compiler cannot find packages for import statements.
>>
>> Thanks for any suggestions,
>>
>> Patricia
>>
>>
>> On 7/12/2010 7:57 AM, Gregg Wonderly wrote:
>>> As a general rule, there is no reason to use '\' in java paths that are
>>> passed into any class that uses the path inside of the JVM. Only when
>>> you use Runtime.exec() et.al. do you need to worry about '/' vs '\'.
>>> Windows, a long time ago, recognized '/' internally as a path separator,
>>> because only the 'shell' was dealing with '/' as an option delimiter.
>>>
>>> It makes life a lot easier to just use '/' for java.lang.File paths and
>>> in particular, it simplifies property file and other text usage where
>>> '\' is interpreted by the class as a special character.
>>>
>>> Gregg Wonderly
>>>
>>> Patricia Shanahan wrote:
>>>> Promising. I got error messages at first because I forgot to double up
>>>> the "/" characters, so it was paying attention to the jtreg.dir line.
>>>> Once I fixed that it went to:
>>>>
>>>> Buildfile: C:\apache\river\jtsk\trunk\qa\build.xml
>>>>
>>>> jtreg:
>>>> [mkdir] Created dir: C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
>>>> [move] Moving 4 files to C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
>>>> [move] Moving 1 file to C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
>>>> [move] Moving 1 file to C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
>>>>
>>>> BUILD FAILED
>>>> C:\apache\river\jtsk\trunk\qa\build.xml:156: Cannot determine test
>>>> suite from test (is TEST.ROOT missing?):
>>>> C:\apache\river\jtsk\qa\jtreg\JTlib-tmp\concurrent-policy-util.jar
>>>>
>>>> Total time: 1 second
>>>>
>>>>
>>>> What do you think it would like for TEST.ROOT?
>>>>
>>>>
>>>> On 7/9/2010 11:55 PM, Peter Firmstone wrote:
>>>>> Try adding this to your build.properties file:
>>>>>
>>>>> jtreg.dir=C:\apache\river\jtsk\qa\jtreg
>>>>>
>>>>> Peter.
>>>>>
>>>>> Patricia Shanahan wrote:
>>>>>> Yes, I ran it in the root directory.
>>>>>>
>>>>>>
>>>>>> Patricia
>>>>>>
>>>>>> On Jul 9, 2010, at 21:35, Peter Firmstone <ji...@zeus.net.au> wrote:
>>>>>>
>>>>>>> It appears as though it can't see the jar archives in the directory:
>>>>>>>
>>>>>>> C;\apache\river\jtsk\trunk\lib\
>>>>>>>
>>>>>>> The missing class is from jsk-platform.jar
>>>>>>>
>>>>>>> Did you run ant all.build first?
>>>>>>>
>>>>>>> Cheers,
>>>>>>>
>>>>>>> Peter.
>>>>>>>
>>>>>>> Patricia Shanahan wrote:
>>>>>>>> Sure:
>>>>>>>>
>>>>>>>> http://www.patriciashanahan.com/apache/myJTREGLog.txt
>>>>>>>>
>>>>>>>> Patricia
>>>>>>>>
>>>>>>>>
>>>>>>>> On 7/9/2010 7:59 PM, Peter Firmstone wrote:
>>>>>>>>> Can you dump the output to a text file and submit it?
>>>>>>>>>
>>>>>>>>> Peter.
>>>>>>>>>
>>>>>>>>> Patricia Shanahan wrote:
>>>>>>>>>> I tried that. It didn't seem to make any difference.
>>>>>>>>>>
>>>>>>>>>> Patricia
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On 7/9/2010 4:48 PM, Peter Firmstone wrote:
>>>>>>>>>>> Try copying your existing build.properties file to the qa
>>>>>>>>>>> directory,
>>>>>>>>>>> just for now.
>>>>>>>>>>>
>>>>>>>>>>> Then try the jtreg tests again too.
>>>>>>>>>>>
>>>>>>>>>>> Cheers,
>>>>>>>>>>>
>>>>>>>>>>> Peter.
>>>>>>>>>>>
>>>>>>>>>>> Patricia Shanahan wrote:
>>>>>>>>>>>> The problem seems to be a classpath issue when compiling the
>>>>>>>>>>>> tests. I
>>>>>>>>>>>> get messages of the form:
>>>>>>>>>>>>
>>>>>>>>>>>> C:\\apache\\river\\jtsk\\trunk\\qa\\jtreg\\com\\sun\\jini\\action\\catchSecurityException\\CatchSecurityException.java:30:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> package com.sun.jini.action does not exist
>>>>>>>>>>>> import com.sun.jini.action.GetBooleanAction;
>>>>>>>>>>>>
>>>>>>>>>>>> Do I need another build.properties file in the qa directory?
>>>>>>>>>>>> If so,
>>>>>>>>>>>> what should it contain?
>>>>>>>>>>>>
>>>>>>>>>>>> Patricia
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On 7/9/2010 4:04 AM, Peter Firmstone wrote:
>>>>>>>>>>>>> Have you tried the jtreg tests?
>>>>>>>>>>>>>
>>>>>>>>>>>>> The results of the jtreg tests will appear under
>>>>>>>>>>>>> trunk/qa/jtreg
>>>>>>>>>>>>>
>>>>>>>>>>>>> jtreg constructs a web page index with detailed result
>>>>>>>>>>>>> pages for
>>>>>>>>>>>>> failed
>>>>>>>>>>>>> tests.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Cheers,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Peter.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Patricia Shanahan wrote:
>>>>>>>>>>>>>> On of the simplifying steps I took to try to set up River
>>>>>>>>>>>>>> development
>>>>>>>>>>>>>> on a Windows box was use of a space-free path. I have since
>>>>>>>>>>>>>> retested
>>>>>>>>>>>>>> under "My Documents" and get QA test failures of the form:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [java] com.sun.jini.qa.harness.TestException:
>>>>>>>>>>>>>> [java]
>>>>>>>>>>>>>> getResource(com/sun/jini/test/spec/loader/util/resources/files/file02)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [java]
>>>>>>>>>>>>>> returned:jar:file:/C:/Documents%20and%20Settings/Administrator/My%20Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [java] expected:jar:file:/C:/Documents and
>>>>>>>>>>>>>> Settings/Administrator/My
>>>>>>>>>>>>>> Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [java] at
>>>>>>>>>>>>>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.testCase(Unknown
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Source)
>>>>>>>>>>>>>> [java] at
>>>>>>>>>>>>>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.run(Unknown
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Source)
>>>>>>>>>>>>>> [java] at com.sun.jini.qa.harness.MasterTest.doTest(Unknown
>>>>>>>>>>>>>> Source)
>>>>>>>>>>>>>> [java] at com.sun.jini.qa.harness.MasterTest.main(Unknown
>>>>>>>>>>>>>> Source)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> The expected URL leaves the spaces as spaces. The returned
>>>>>>>>>>>>>> URL
>>>>>>>>>>>>>> has
>>>>>>>>>>>>>> the
>>>>>>>>>>>>>> spaces replaced, as is normal inside a URL, by %20.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Patricia
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
Re: QA tests and spaces in file names
Posted by Peter Firmstone <ji...@zeus.net.au>.
My comments here might also be of assistance:
https://issues.apache.org/jira/browse/RIVER-319
Patricia Shanahan wrote:
> Correct. I did try using only "/" as path separator, and it still
> failed. Here is my latest build.properties:
>
> bash-3.2$ pwd
> /cygdrive/c/apache/river/jtsk/trunk/qa
> bash-3.2$ cat build.properties
> river.home=c:/apache/river/jtsk/trunk
> jtreg.home=c:/apache/jtreg
> jtreg.dir=C:/apache/river/jtsk/trunk/qa/jtreg
> jdk1.5.home=C:/Program Files (x86)/Java/jdk1.5.0_22
>
> The output is in http://www.patriciashanahan.com/apache/myJTREGLog.txt
>
> Maybe somebody could make available to me the output from a correct
> regression test? Part of my problem is that, being unfamiliar with
> River, the Apache development flow in general, and JTreg in
> particular, I don't know what output to expect.
>
> The problems look to me rather like a compile-time classpath problem -
> files are found if the scripts are looking for them directly, but the
> compiler cannot find packages for import statements.
>
> Thanks for any suggestions,
>
> Patricia
>
>
> On 7/12/2010 7:57 AM, Gregg Wonderly wrote:
>> As a general rule, there is no reason to use '\' in java paths that are
>> passed into any class that uses the path inside of the JVM. Only when
>> you use Runtime.exec() et.al. do you need to worry about '/' vs '\'.
>> Windows, a long time ago, recognized '/' internally as a path separator,
>> because only the 'shell' was dealing with '/' as an option delimiter.
>>
>> It makes life a lot easier to just use '/' for java.lang.File paths and
>> in particular, it simplifies property file and other text usage where
>> '\' is interpreted by the class as a special character.
>>
>> Gregg Wonderly
>>
>> Patricia Shanahan wrote:
>>> Promising. I got error messages at first because I forgot to double up
>>> the "/" characters, so it was paying attention to the jtreg.dir line.
>>> Once I fixed that it went to:
>>>
>>> Buildfile: C:\apache\river\jtsk\trunk\qa\build.xml
>>>
>>> jtreg:
>>> [mkdir] Created dir: C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
>>> [move] Moving 4 files to C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
>>> [move] Moving 1 file to C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
>>> [move] Moving 1 file to C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
>>>
>>> BUILD FAILED
>>> C:\apache\river\jtsk\trunk\qa\build.xml:156: Cannot determine test
>>> suite from test (is TEST.ROOT missing?):
>>> C:\apache\river\jtsk\qa\jtreg\JTlib-tmp\concurrent-policy-util.jar
>>>
>>> Total time: 1 second
>>>
>>>
>>> What do you think it would like for TEST.ROOT?
>>>
>>>
>>> On 7/9/2010 11:55 PM, Peter Firmstone wrote:
>>>> Try adding this to your build.properties file:
>>>>
>>>> jtreg.dir=C:\apache\river\jtsk\qa\jtreg
>>>>
>>>> Peter.
>>>>
>>>> Patricia Shanahan wrote:
>>>>> Yes, I ran it in the root directory.
>>>>>
>>>>>
>>>>> Patricia
>>>>>
>>>>> On Jul 9, 2010, at 21:35, Peter Firmstone <ji...@zeus.net.au> wrote:
>>>>>
>>>>>> It appears as though it can't see the jar archives in the directory:
>>>>>>
>>>>>> C;\apache\river\jtsk\trunk\lib\
>>>>>>
>>>>>> The missing class is from jsk-platform.jar
>>>>>>
>>>>>> Did you run ant all.build first?
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> Peter.
>>>>>>
>>>>>> Patricia Shanahan wrote:
>>>>>>> Sure:
>>>>>>>
>>>>>>> http://www.patriciashanahan.com/apache/myJTREGLog.txt
>>>>>>>
>>>>>>> Patricia
>>>>>>>
>>>>>>>
>>>>>>> On 7/9/2010 7:59 PM, Peter Firmstone wrote:
>>>>>>>> Can you dump the output to a text file and submit it?
>>>>>>>>
>>>>>>>> Peter.
>>>>>>>>
>>>>>>>> Patricia Shanahan wrote:
>>>>>>>>> I tried that. It didn't seem to make any difference.
>>>>>>>>>
>>>>>>>>> Patricia
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 7/9/2010 4:48 PM, Peter Firmstone wrote:
>>>>>>>>>> Try copying your existing build.properties file to the qa
>>>>>>>>>> directory,
>>>>>>>>>> just for now.
>>>>>>>>>>
>>>>>>>>>> Then try the jtreg tests again too.
>>>>>>>>>>
>>>>>>>>>> Cheers,
>>>>>>>>>>
>>>>>>>>>> Peter.
>>>>>>>>>>
>>>>>>>>>> Patricia Shanahan wrote:
>>>>>>>>>>> The problem seems to be a classpath issue when compiling the
>>>>>>>>>>> tests. I
>>>>>>>>>>> get messages of the form:
>>>>>>>>>>>
>>>>>>>>>>> C:\\apache\\river\\jtsk\\trunk\\qa\\jtreg\\com\\sun\\jini\\action\\catchSecurityException\\CatchSecurityException.java:30:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> package com.sun.jini.action does not exist
>>>>>>>>>>> import com.sun.jini.action.GetBooleanAction;
>>>>>>>>>>>
>>>>>>>>>>> Do I need another build.properties file in the qa directory?
>>>>>>>>>>> If so,
>>>>>>>>>>> what should it contain?
>>>>>>>>>>>
>>>>>>>>>>> Patricia
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On 7/9/2010 4:04 AM, Peter Firmstone wrote:
>>>>>>>>>>>> Have you tried the jtreg tests?
>>>>>>>>>>>>
>>>>>>>>>>>> The results of the jtreg tests will appear under
>>>>>>>>>>>> trunk/qa/jtreg
>>>>>>>>>>>>
>>>>>>>>>>>> jtreg constructs a web page index with detailed result
>>>>>>>>>>>> pages for
>>>>>>>>>>>> failed
>>>>>>>>>>>> tests.
>>>>>>>>>>>>
>>>>>>>>>>>> Cheers,
>>>>>>>>>>>>
>>>>>>>>>>>> Peter.
>>>>>>>>>>>>
>>>>>>>>>>>> Patricia Shanahan wrote:
>>>>>>>>>>>>> On of the simplifying steps I took to try to set up River
>>>>>>>>>>>>> development
>>>>>>>>>>>>> on a Windows box was use of a space-free path. I have since
>>>>>>>>>>>>> retested
>>>>>>>>>>>>> under "My Documents" and get QA test failures of the form:
>>>>>>>>>>>>>
>>>>>>>>>>>>> [java] com.sun.jini.qa.harness.TestException:
>>>>>>>>>>>>> [java]
>>>>>>>>>>>>> getResource(com/sun/jini/test/spec/loader/util/resources/files/file02)
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> [java]
>>>>>>>>>>>>> returned:jar:file:/C:/Documents%20and%20Settings/Administrator/My%20Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> [java] expected:jar:file:/C:/Documents and
>>>>>>>>>>>>> Settings/Administrator/My
>>>>>>>>>>>>> Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> [java] at
>>>>>>>>>>>>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.testCase(Unknown
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Source)
>>>>>>>>>>>>> [java] at
>>>>>>>>>>>>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.run(Unknown
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Source)
>>>>>>>>>>>>> [java] at com.sun.jini.qa.harness.MasterTest.doTest(Unknown
>>>>>>>>>>>>> Source)
>>>>>>>>>>>>> [java] at com.sun.jini.qa.harness.MasterTest.main(Unknown
>>>>>>>>>>>>> Source)
>>>>>>>>>>>>>
>>>>>>>>>>>>> The expected URL leaves the spaces as spaces. The returned
>>>>>>>>>>>>> URL
>>>>>>>>>>>>> has
>>>>>>>>>>>>> the
>>>>>>>>>>>>> spaces replaced, as is normal inside a URL, by %20.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Patricia
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
Re: QA tests and spaces in file names
Posted by Patricia Shanahan <pa...@acm.org>.
Correct. I did try using only "/" as path separator, and it still
failed. Here is my latest build.properties:
bash-3.2$ pwd
/cygdrive/c/apache/river/jtsk/trunk/qa
bash-3.2$ cat build.properties
river.home=c:/apache/river/jtsk/trunk
jtreg.home=c:/apache/jtreg
jtreg.dir=C:/apache/river/jtsk/trunk/qa/jtreg
jdk1.5.home=C:/Program Files (x86)/Java/jdk1.5.0_22
The output is in http://www.patriciashanahan.com/apache/myJTREGLog.txt
Maybe somebody could make available to me the output from a correct
regression test? Part of my problem is that, being unfamiliar with
River, the Apache development flow in general, and JTreg in particular,
I don't know what output to expect.
The problems look to me rather like a compile-time classpath problem -
files are found if the scripts are looking for them directly, but the
compiler cannot find packages for import statements.
Thanks for any suggestions,
Patricia
On 7/12/2010 7:57 AM, Gregg Wonderly wrote:
> As a general rule, there is no reason to use '\' in java paths that are
> passed into any class that uses the path inside of the JVM. Only when
> you use Runtime.exec() et.al. do you need to worry about '/' vs '\'.
> Windows, a long time ago, recognized '/' internally as a path separator,
> because only the 'shell' was dealing with '/' as an option delimiter.
>
> It makes life a lot easier to just use '/' for java.lang.File paths and
> in particular, it simplifies property file and other text usage where
> '\' is interpreted by the class as a special character.
>
> Gregg Wonderly
>
> Patricia Shanahan wrote:
>> Promising. I got error messages at first because I forgot to double up
>> the "/" characters, so it was paying attention to the jtreg.dir line.
>> Once I fixed that it went to:
>>
>> Buildfile: C:\apache\river\jtsk\trunk\qa\build.xml
>>
>> jtreg:
>> [mkdir] Created dir: C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
>> [move] Moving 4 files to C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
>> [move] Moving 1 file to C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
>> [move] Moving 1 file to C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
>>
>> BUILD FAILED
>> C:\apache\river\jtsk\trunk\qa\build.xml:156: Cannot determine test
>> suite from test (is TEST.ROOT missing?):
>> C:\apache\river\jtsk\qa\jtreg\JTlib-tmp\concurrent-policy-util.jar
>>
>> Total time: 1 second
>>
>>
>> What do you think it would like for TEST.ROOT?
>>
>>
>> On 7/9/2010 11:55 PM, Peter Firmstone wrote:
>>> Try adding this to your build.properties file:
>>>
>>> jtreg.dir=C:\apache\river\jtsk\qa\jtreg
>>>
>>> Peter.
>>>
>>> Patricia Shanahan wrote:
>>>> Yes, I ran it in the root directory.
>>>>
>>>>
>>>> Patricia
>>>>
>>>> On Jul 9, 2010, at 21:35, Peter Firmstone <ji...@zeus.net.au> wrote:
>>>>
>>>>> It appears as though it can't see the jar archives in the directory:
>>>>>
>>>>> C;\apache\river\jtsk\trunk\lib\
>>>>>
>>>>> The missing class is from jsk-platform.jar
>>>>>
>>>>> Did you run ant all.build first?
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Peter.
>>>>>
>>>>> Patricia Shanahan wrote:
>>>>>> Sure:
>>>>>>
>>>>>> http://www.patriciashanahan.com/apache/myJTREGLog.txt
>>>>>>
>>>>>> Patricia
>>>>>>
>>>>>>
>>>>>> On 7/9/2010 7:59 PM, Peter Firmstone wrote:
>>>>>>> Can you dump the output to a text file and submit it?
>>>>>>>
>>>>>>> Peter.
>>>>>>>
>>>>>>> Patricia Shanahan wrote:
>>>>>>>> I tried that. It didn't seem to make any difference.
>>>>>>>>
>>>>>>>> Patricia
>>>>>>>>
>>>>>>>>
>>>>>>>> On 7/9/2010 4:48 PM, Peter Firmstone wrote:
>>>>>>>>> Try copying your existing build.properties file to the qa
>>>>>>>>> directory,
>>>>>>>>> just for now.
>>>>>>>>>
>>>>>>>>> Then try the jtreg tests again too.
>>>>>>>>>
>>>>>>>>> Cheers,
>>>>>>>>>
>>>>>>>>> Peter.
>>>>>>>>>
>>>>>>>>> Patricia Shanahan wrote:
>>>>>>>>>> The problem seems to be a classpath issue when compiling the
>>>>>>>>>> tests. I
>>>>>>>>>> get messages of the form:
>>>>>>>>>>
>>>>>>>>>> C:\\apache\\river\\jtsk\\trunk\\qa\\jtreg\\com\\sun\\jini\\action\\catchSecurityException\\CatchSecurityException.java:30:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> package com.sun.jini.action does not exist
>>>>>>>>>> import com.sun.jini.action.GetBooleanAction;
>>>>>>>>>>
>>>>>>>>>> Do I need another build.properties file in the qa directory?
>>>>>>>>>> If so,
>>>>>>>>>> what should it contain?
>>>>>>>>>>
>>>>>>>>>> Patricia
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On 7/9/2010 4:04 AM, Peter Firmstone wrote:
>>>>>>>>>>> Have you tried the jtreg tests?
>>>>>>>>>>>
>>>>>>>>>>> The results of the jtreg tests will appear under trunk/qa/jtreg
>>>>>>>>>>>
>>>>>>>>>>> jtreg constructs a web page index with detailed result pages for
>>>>>>>>>>> failed
>>>>>>>>>>> tests.
>>>>>>>>>>>
>>>>>>>>>>> Cheers,
>>>>>>>>>>>
>>>>>>>>>>> Peter.
>>>>>>>>>>>
>>>>>>>>>>> Patricia Shanahan wrote:
>>>>>>>>>>>> On of the simplifying steps I took to try to set up River
>>>>>>>>>>>> development
>>>>>>>>>>>> on a Windows box was use of a space-free path. I have since
>>>>>>>>>>>> retested
>>>>>>>>>>>> under "My Documents" and get QA test failures of the form:
>>>>>>>>>>>>
>>>>>>>>>>>> [java] com.sun.jini.qa.harness.TestException:
>>>>>>>>>>>> [java]
>>>>>>>>>>>> getResource(com/sun/jini/test/spec/loader/util/resources/files/file02)
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> [java]
>>>>>>>>>>>> returned:jar:file:/C:/Documents%20and%20Settings/Administrator/My%20Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> [java] expected:jar:file:/C:/Documents and
>>>>>>>>>>>> Settings/Administrator/My
>>>>>>>>>>>> Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> [java] at
>>>>>>>>>>>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.testCase(Unknown
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Source)
>>>>>>>>>>>> [java] at
>>>>>>>>>>>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.run(Unknown
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Source)
>>>>>>>>>>>> [java] at com.sun.jini.qa.harness.MasterTest.doTest(Unknown
>>>>>>>>>>>> Source)
>>>>>>>>>>>> [java] at com.sun.jini.qa.harness.MasterTest.main(Unknown
>>>>>>>>>>>> Source)
>>>>>>>>>>>>
>>>>>>>>>>>> The expected URL leaves the spaces as spaces. The returned URL
>>>>>>>>>>>> has
>>>>>>>>>>>> the
>>>>>>>>>>>> spaces replaced, as is normal inside a URL, by %20.
>>>>>>>>>>>>
>>>>>>>>>>>> Patricia
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>
>>
>
>
Re: QA tests and spaces in file names
Posted by Gregg Wonderly <gr...@wonderly.org>.
As a general rule, there is no reason to use '\' in java paths that are passed
into any class that uses the path inside of the JVM. Only when you use
Runtime.exec() et.al. do you need to worry about '/' vs '\'. Windows, a long
time ago, recognized '/' internally as a path separator, because only the
'shell' was dealing with '/' as an option delimiter.
It makes life a lot easier to just use '/' for java.lang.File paths and in
particular, it simplifies property file and other text usage where '\' is
interpreted by the class as a special character.
Gregg Wonderly
Patricia Shanahan wrote:
> Promising. I got error messages at first because I forgot to double up
> the "/" characters, so it was paying attention to the jtreg.dir line.
> Once I fixed that it went to:
>
> Buildfile: C:\apache\river\jtsk\trunk\qa\build.xml
>
> jtreg:
> [mkdir] Created dir: C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
> [move] Moving 4 files to C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
> [move] Moving 1 file to C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
> [move] Moving 1 file to C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
>
> BUILD FAILED
> C:\apache\river\jtsk\trunk\qa\build.xml:156: Cannot determine test suite
> from test (is TEST.ROOT missing?):
> C:\apache\river\jtsk\qa\jtreg\JTlib-tmp\concurrent-policy-util.jar
>
> Total time: 1 second
>
>
> What do you think it would like for TEST.ROOT?
>
>
> On 7/9/2010 11:55 PM, Peter Firmstone wrote:
>> Try adding this to your build.properties file:
>>
>> jtreg.dir=C:\apache\river\jtsk\qa\jtreg
>>
>> Peter.
>>
>> Patricia Shanahan wrote:
>>> Yes, I ran it in the root directory.
>>>
>>>
>>> Patricia
>>>
>>> On Jul 9, 2010, at 21:35, Peter Firmstone <ji...@zeus.net.au> wrote:
>>>
>>>> It appears as though it can't see the jar archives in the directory:
>>>>
>>>> C;\apache\river\jtsk\trunk\lib\
>>>>
>>>> The missing class is from jsk-platform.jar
>>>>
>>>> Did you run ant all.build first?
>>>>
>>>> Cheers,
>>>>
>>>> Peter.
>>>>
>>>> Patricia Shanahan wrote:
>>>>> Sure:
>>>>>
>>>>> http://www.patriciashanahan.com/apache/myJTREGLog.txt
>>>>>
>>>>> Patricia
>>>>>
>>>>>
>>>>> On 7/9/2010 7:59 PM, Peter Firmstone wrote:
>>>>>> Can you dump the output to a text file and submit it?
>>>>>>
>>>>>> Peter.
>>>>>>
>>>>>> Patricia Shanahan wrote:
>>>>>>> I tried that. It didn't seem to make any difference.
>>>>>>>
>>>>>>> Patricia
>>>>>>>
>>>>>>>
>>>>>>> On 7/9/2010 4:48 PM, Peter Firmstone wrote:
>>>>>>>> Try copying your existing build.properties file to the qa
>>>>>>>> directory,
>>>>>>>> just for now.
>>>>>>>>
>>>>>>>> Then try the jtreg tests again too.
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>>
>>>>>>>> Peter.
>>>>>>>>
>>>>>>>> Patricia Shanahan wrote:
>>>>>>>>> The problem seems to be a classpath issue when compiling the
>>>>>>>>> tests. I
>>>>>>>>> get messages of the form:
>>>>>>>>>
>>>>>>>>> C:\\apache\\river\\jtsk\\trunk\\qa\\jtreg\\com\\sun\\jini\\action\\catchSecurityException\\CatchSecurityException.java:30:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> package com.sun.jini.action does not exist
>>>>>>>>> import com.sun.jini.action.GetBooleanAction;
>>>>>>>>>
>>>>>>>>> Do I need another build.properties file in the qa directory? If
>>>>>>>>> so,
>>>>>>>>> what should it contain?
>>>>>>>>>
>>>>>>>>> Patricia
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 7/9/2010 4:04 AM, Peter Firmstone wrote:
>>>>>>>>>> Have you tried the jtreg tests?
>>>>>>>>>>
>>>>>>>>>> The results of the jtreg tests will appear under trunk/qa/jtreg
>>>>>>>>>>
>>>>>>>>>> jtreg constructs a web page index with detailed result pages for
>>>>>>>>>> failed
>>>>>>>>>> tests.
>>>>>>>>>>
>>>>>>>>>> Cheers,
>>>>>>>>>>
>>>>>>>>>> Peter.
>>>>>>>>>>
>>>>>>>>>> Patricia Shanahan wrote:
>>>>>>>>>>> On of the simplifying steps I took to try to set up River
>>>>>>>>>>> development
>>>>>>>>>>> on a Windows box was use of a space-free path. I have since
>>>>>>>>>>> retested
>>>>>>>>>>> under "My Documents" and get QA test failures of the form:
>>>>>>>>>>>
>>>>>>>>>>> [java] com.sun.jini.qa.harness.TestException:
>>>>>>>>>>> [java]
>>>>>>>>>>> getResource(com/sun/jini/test/spec/loader/util/resources/files/file02)
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> [java]
>>>>>>>>>>> returned:jar:file:/C:/Documents%20and%20Settings/Administrator/My%20Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> [java] expected:jar:file:/C:/Documents and
>>>>>>>>>>> Settings/Administrator/My
>>>>>>>>>>> Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> [java] at
>>>>>>>>>>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.testCase(Unknown
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Source)
>>>>>>>>>>> [java] at
>>>>>>>>>>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.run(Unknown
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Source)
>>>>>>>>>>> [java] at com.sun.jini.qa.harness.MasterTest.doTest(Unknown
>>>>>>>>>>> Source)
>>>>>>>>>>> [java] at com.sun.jini.qa.harness.MasterTest.main(Unknown
>>>>>>>>>>> Source)
>>>>>>>>>>>
>>>>>>>>>>> The expected URL leaves the spaces as spaces. The returned URL
>>>>>>>>>>> has
>>>>>>>>>>> the
>>>>>>>>>>> spaces replaced, as is normal inside a URL, by %20.
>>>>>>>>>>>
>>>>>>>>>>> Patricia
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>>
>
>
Re: QA tests and spaces in file names
Posted by Patricia Shanahan <pa...@acm.org>.
Promising. I got error messages at first because I forgot to double up
the "/" characters, so it was paying attention to the jtreg.dir line.
Once I fixed that it went to:
Buildfile: C:\apache\river\jtsk\trunk\qa\build.xml
jtreg:
[mkdir] Created dir: C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
[move] Moving 4 files to C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
[move] Moving 1 file to C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
[move] Moving 1 file to C:\apache\river\jtsk\qa\jtreg\JTlib-tmp
BUILD FAILED
C:\apache\river\jtsk\trunk\qa\build.xml:156: Cannot determine test suite
from test (is TEST.ROOT missing?):
C:\apache\river\jtsk\qa\jtreg\JTlib-tmp\concurrent-policy-util.jar
Total time: 1 second
What do you think it would like for TEST.ROOT?
On 7/9/2010 11:55 PM, Peter Firmstone wrote:
> Try adding this to your build.properties file:
>
> jtreg.dir=C:\apache\river\jtsk\qa\jtreg
>
> Peter.
>
> Patricia Shanahan wrote:
>> Yes, I ran it in the root directory.
>>
>>
>> Patricia
>>
>> On Jul 9, 2010, at 21:35, Peter Firmstone <ji...@zeus.net.au> wrote:
>>
>>> It appears as though it can't see the jar archives in the directory:
>>>
>>> C;\apache\river\jtsk\trunk\lib\
>>>
>>> The missing class is from jsk-platform.jar
>>>
>>> Did you run ant all.build first?
>>>
>>> Cheers,
>>>
>>> Peter.
>>>
>>> Patricia Shanahan wrote:
>>>> Sure:
>>>>
>>>> http://www.patriciashanahan.com/apache/myJTREGLog.txt
>>>>
>>>> Patricia
>>>>
>>>>
>>>> On 7/9/2010 7:59 PM, Peter Firmstone wrote:
>>>>> Can you dump the output to a text file and submit it?
>>>>>
>>>>> Peter.
>>>>>
>>>>> Patricia Shanahan wrote:
>>>>>> I tried that. It didn't seem to make any difference.
>>>>>>
>>>>>> Patricia
>>>>>>
>>>>>>
>>>>>> On 7/9/2010 4:48 PM, Peter Firmstone wrote:
>>>>>>> Try copying your existing build.properties file to the qa directory,
>>>>>>> just for now.
>>>>>>>
>>>>>>> Then try the jtreg tests again too.
>>>>>>>
>>>>>>> Cheers,
>>>>>>>
>>>>>>> Peter.
>>>>>>>
>>>>>>> Patricia Shanahan wrote:
>>>>>>>> The problem seems to be a classpath issue when compiling the
>>>>>>>> tests. I
>>>>>>>> get messages of the form:
>>>>>>>>
>>>>>>>> C:\\apache\\river\\jtsk\\trunk\\qa\\jtreg\\com\\sun\\jini\\action\\catchSecurityException\\CatchSecurityException.java:30:
>>>>>>>>
>>>>>>>>
>>>>>>>> package com.sun.jini.action does not exist
>>>>>>>> import com.sun.jini.action.GetBooleanAction;
>>>>>>>>
>>>>>>>> Do I need another build.properties file in the qa directory? If so,
>>>>>>>> what should it contain?
>>>>>>>>
>>>>>>>> Patricia
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On 7/9/2010 4:04 AM, Peter Firmstone wrote:
>>>>>>>>> Have you tried the jtreg tests?
>>>>>>>>>
>>>>>>>>> The results of the jtreg tests will appear under trunk/qa/jtreg
>>>>>>>>>
>>>>>>>>> jtreg constructs a web page index with detailed result pages for
>>>>>>>>> failed
>>>>>>>>> tests.
>>>>>>>>>
>>>>>>>>> Cheers,
>>>>>>>>>
>>>>>>>>> Peter.
>>>>>>>>>
>>>>>>>>> Patricia Shanahan wrote:
>>>>>>>>>> On of the simplifying steps I took to try to set up River
>>>>>>>>>> development
>>>>>>>>>> on a Windows box was use of a space-free path. I have since
>>>>>>>>>> retested
>>>>>>>>>> under "My Documents" and get QA test failures of the form:
>>>>>>>>>>
>>>>>>>>>> [java] com.sun.jini.qa.harness.TestException:
>>>>>>>>>> [java]
>>>>>>>>>> getResource(com/sun/jini/test/spec/loader/util/resources/files/file02)
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> [java]
>>>>>>>>>> returned:jar:file:/C:/Documents%20and%20Settings/Administrator/My%20Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> [java] expected:jar:file:/C:/Documents and
>>>>>>>>>> Settings/Administrator/My
>>>>>>>>>> Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> [java] at
>>>>>>>>>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.testCase(Unknown
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Source)
>>>>>>>>>> [java] at
>>>>>>>>>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.run(Unknown
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Source)
>>>>>>>>>> [java] at com.sun.jini.qa.harness.MasterTest.doTest(Unknown
>>>>>>>>>> Source)
>>>>>>>>>> [java] at com.sun.jini.qa.harness.MasterTest.main(Unknown Source)
>>>>>>>>>>
>>>>>>>>>> The expected URL leaves the spaces as spaces. The returned URL
>>>>>>>>>> has
>>>>>>>>>> the
>>>>>>>>>> spaces replaced, as is normal inside a URL, by %20.
>>>>>>>>>>
>>>>>>>>>> Patricia
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>
>
Re: QA tests and spaces in file names
Posted by Peter Firmstone <ji...@zeus.net.au>.
Try adding this to your build.properties file:
jtreg.dir=C:\apache\river\jtsk\qa\jtreg
Peter.
Patricia Shanahan wrote:
> Yes, I ran it in the root directory.
>
>
> Patricia
>
> On Jul 9, 2010, at 21:35, Peter Firmstone <ji...@zeus.net.au> wrote:
>
>> It appears as though it can't see the jar archives in the directory:
>>
>> C;\apache\river\jtsk\trunk\lib\
>>
>> The missing class is from jsk-platform.jar
>>
>> Did you run ant all.build first?
>>
>> Cheers,
>>
>> Peter.
>>
>> Patricia Shanahan wrote:
>>> Sure:
>>>
>>> http://www.patriciashanahan.com/apache/myJTREGLog.txt
>>>
>>> Patricia
>>>
>>>
>>> On 7/9/2010 7:59 PM, Peter Firmstone wrote:
>>>> Can you dump the output to a text file and submit it?
>>>>
>>>> Peter.
>>>>
>>>> Patricia Shanahan wrote:
>>>>> I tried that. It didn't seem to make any difference.
>>>>>
>>>>> Patricia
>>>>>
>>>>>
>>>>> On 7/9/2010 4:48 PM, Peter Firmstone wrote:
>>>>>> Try copying your existing build.properties file to the qa directory,
>>>>>> just for now.
>>>>>>
>>>>>> Then try the jtreg tests again too.
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> Peter.
>>>>>>
>>>>>> Patricia Shanahan wrote:
>>>>>>> The problem seems to be a classpath issue when compiling the
>>>>>>> tests. I
>>>>>>> get messages of the form:
>>>>>>>
>>>>>>> C:\\apache\\river\\jtsk\\trunk\\qa\\jtreg\\com\\sun\\jini\\action\\catchSecurityException\\CatchSecurityException.java:30:
>>>>>>>
>>>>>>>
>>>>>>> package com.sun.jini.action does not exist
>>>>>>> import com.sun.jini.action.GetBooleanAction;
>>>>>>>
>>>>>>> Do I need another build.properties file in the qa directory? If so,
>>>>>>> what should it contain?
>>>>>>>
>>>>>>> Patricia
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On 7/9/2010 4:04 AM, Peter Firmstone wrote:
>>>>>>>> Have you tried the jtreg tests?
>>>>>>>>
>>>>>>>> The results of the jtreg tests will appear under trunk/qa/jtreg
>>>>>>>>
>>>>>>>> jtreg constructs a web page index with detailed result pages for
>>>>>>>> failed
>>>>>>>> tests.
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>>
>>>>>>>> Peter.
>>>>>>>>
>>>>>>>> Patricia Shanahan wrote:
>>>>>>>>> On of the simplifying steps I took to try to set up River
>>>>>>>>> development
>>>>>>>>> on a Windows box was use of a space-free path. I have since
>>>>>>>>> retested
>>>>>>>>> under "My Documents" and get QA test failures of the form:
>>>>>>>>>
>>>>>>>>> [java] com.sun.jini.qa.harness.TestException:
>>>>>>>>> [java]
>>>>>>>>> getResource(com/sun/jini/test/spec/loader/util/resources/files/file02)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> [java]
>>>>>>>>> returned:jar:file:/C:/Documents%20and%20Settings/Administrator/My%20Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> [java] expected:jar:file:/C:/Documents and
>>>>>>>>> Settings/Administrator/My
>>>>>>>>> Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> [java] at
>>>>>>>>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.testCase(Unknown
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Source)
>>>>>>>>> [java] at
>>>>>>>>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.run(Unknown
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Source)
>>>>>>>>> [java] at com.sun.jini.qa.harness.MasterTest.doTest(Unknown
>>>>>>>>> Source)
>>>>>>>>> [java] at com.sun.jini.qa.harness.MasterTest.main(Unknown Source)
>>>>>>>>>
>>>>>>>>> The expected URL leaves the spaces as spaces. The returned URL
>>>>>>>>> has
>>>>>>>>> the
>>>>>>>>> spaces replaced, as is normal inside a URL, by %20.
>>>>>>>>>
>>>>>>>>> Patricia
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
Re: QA tests and spaces in file names
Posted by Patricia Shanahan <pa...@acm.org>.
Yes, I ran it in the root directory.
Patricia
On Jul 9, 2010, at 21:35, Peter Firmstone <ji...@zeus.net.au> wrote:
> It appears as though it can't see the jar archives in the directory:
>
> C;\apache\river\jtsk\trunk\lib\
>
> The missing class is from jsk-platform.jar
>
> Did you run ant all.build first?
>
> Cheers,
>
> Peter.
>
> Patricia Shanahan wrote:
>> Sure:
>>
>> http://www.patriciashanahan.com/apache/myJTREGLog.txt
>>
>> Patricia
>>
>>
>> On 7/9/2010 7:59 PM, Peter Firmstone wrote:
>>> Can you dump the output to a text file and submit it?
>>>
>>> Peter.
>>>
>>> Patricia Shanahan wrote:
>>>> I tried that. It didn't seem to make any difference.
>>>>
>>>> Patricia
>>>>
>>>>
>>>> On 7/9/2010 4:48 PM, Peter Firmstone wrote:
>>>>> Try copying your existing build.properties file to the qa
>>>>> directory,
>>>>> just for now.
>>>>>
>>>>> Then try the jtreg tests again too.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Peter.
>>>>>
>>>>> Patricia Shanahan wrote:
>>>>>> The problem seems to be a classpath issue when compiling the
>>>>>> tests. I
>>>>>> get messages of the form:
>>>>>>
>>>>>> C:\\apache\\river\\jtsk\\trunk\\qa\\jtreg\\com\\sun\\jini\
>>>>>> \action\\catchSecurityException\\CatchSecurityException.java:30:
>>>>>>
>>>>>> package com.sun.jini.action does not exist
>>>>>> import com.sun.jini.action.GetBooleanAction;
>>>>>>
>>>>>> Do I need another build.properties file in the qa directory? If
>>>>>> so,
>>>>>> what should it contain?
>>>>>>
>>>>>> Patricia
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 7/9/2010 4:04 AM, Peter Firmstone wrote:
>>>>>>> Have you tried the jtreg tests?
>>>>>>>
>>>>>>> The results of the jtreg tests will appear under trunk/qa/jtreg
>>>>>>>
>>>>>>> jtreg constructs a web page index with detailed result pages for
>>>>>>> failed
>>>>>>> tests.
>>>>>>>
>>>>>>> Cheers,
>>>>>>>
>>>>>>> Peter.
>>>>>>>
>>>>>>> Patricia Shanahan wrote:
>>>>>>>> On of the simplifying steps I took to try to set up River
>>>>>>>> development
>>>>>>>> on a Windows box was use of a space-free path. I have since
>>>>>>>> retested
>>>>>>>> under "My Documents" and get QA test failures of the form:
>>>>>>>>
>>>>>>>> [java] com.sun.jini.qa.harness.TestException:
>>>>>>>> [java]
>>>>>>>> getResource(com/sun/jini/test/spec/loader/util/resources/
>>>>>>>> files/file02)
>>>>>>>>
>>>>>>>> [java]
>>>>>>>> returned:jar:file:/C:/Documents%20and%20Settings/
>>>>>>>> Administrator/My%20Documents/apache_development/checkout/jtsk/
>>>>>>>> trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/
>>>>>>>> util/resources/files/file02
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> [java] expected:jar:file:/C:/Documents and Settings/
>>>>>>>> Administrator/My
>>>>>>>> Documents/apache_development/checkout/jtsk/trunk/qa/lib/
>>>>>>>> jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/
>>>>>>>> files/file02
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> [java] at
>>>>>>>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.testCase(
>>>>>>>> Unknown
>>>>>>>>
>>>>>>>>
>>>>>>>> Source)
>>>>>>>> [java] at
>>>>>>>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.run(
>>>>>>>> Unknown
>>>>>>>>
>>>>>>>>
>>>>>>>> Source)
>>>>>>>> [java] at com.sun.jini.qa.harness.MasterTest.doTest(Unknown
>>>>>>>> Source)
>>>>>>>> [java] at com.sun.jini.qa.harness.MasterTest.main(Unknown
>>>>>>>> Source)
>>>>>>>>
>>>>>>>> The expected URL leaves the spaces as spaces. The returned
>>>>>>>> URL has
>>>>>>>> the
>>>>>>>> spaces replaced, as is normal inside a URL, by %20.
>>>>>>>>
>>>>>>>> Patricia
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
Re: QA tests and spaces in file names
Posted by Peter Firmstone <ji...@zeus.net.au>.
Actually that's not quite right, it moves the files successfully, first,
so it probably can't see the JTlib-tmp directory for some reason,
probably a unix specific file path somewhere, I'll look into it further.
Peter Firmstone wrote:
> It appears as though it can't see the jar archives in the directory:
>
> C;\apache\river\jtsk\trunk\lib\
>
> The missing class is from jsk-platform.jar
>
> Did you run ant all.build first?
>
> Cheers,
>
> Peter.
>
> Patricia Shanahan wrote:
>> Sure:
>>
>> http://www.patriciashanahan.com/apache/myJTREGLog.txt
>>
>> Patricia
>>
>>
>> On 7/9/2010 7:59 PM, Peter Firmstone wrote:
>>> Can you dump the output to a text file and submit it?
>>>
>>> Peter.
>>>
>>> Patricia Shanahan wrote:
>>>> I tried that. It didn't seem to make any difference.
>>>>
>>>> Patricia
>>>>
>>>>
>>>> On 7/9/2010 4:48 PM, Peter Firmstone wrote:
>>>>> Try copying your existing build.properties file to the qa directory,
>>>>> just for now.
>>>>>
>>>>> Then try the jtreg tests again too.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Peter.
>>>>>
>>>>> Patricia Shanahan wrote:
>>>>>> The problem seems to be a classpath issue when compiling the
>>>>>> tests. I
>>>>>> get messages of the form:
>>>>>>
>>>>>> C:\\apache\\river\\jtsk\\trunk\\qa\\jtreg\\com\\sun\\jini\\action\\catchSecurityException\\CatchSecurityException.java:30:
>>>>>>
>>>>>>
>>>>>> package com.sun.jini.action does not exist
>>>>>> import com.sun.jini.action.GetBooleanAction;
>>>>>>
>>>>>> Do I need another build.properties file in the qa directory? If so,
>>>>>> what should it contain?
>>>>>>
>>>>>> Patricia
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 7/9/2010 4:04 AM, Peter Firmstone wrote:
>>>>>>> Have you tried the jtreg tests?
>>>>>>>
>>>>>>> The results of the jtreg tests will appear under trunk/qa/jtreg
>>>>>>>
>>>>>>> jtreg constructs a web page index with detailed result pages for
>>>>>>> failed
>>>>>>> tests.
>>>>>>>
>>>>>>> Cheers,
>>>>>>>
>>>>>>> Peter.
>>>>>>>
>>>>>>> Patricia Shanahan wrote:
>>>>>>>> On of the simplifying steps I took to try to set up River
>>>>>>>> development
>>>>>>>> on a Windows box was use of a space-free path. I have since
>>>>>>>> retested
>>>>>>>> under "My Documents" and get QA test failures of the form:
>>>>>>>>
>>>>>>>> [java] com.sun.jini.qa.harness.TestException:
>>>>>>>> [java]
>>>>>>>> getResource(com/sun/jini/test/spec/loader/util/resources/files/file02)
>>>>>>>>
>>>>>>>>
>>>>>>>> [java]
>>>>>>>> returned:jar:file:/C:/Documents%20and%20Settings/Administrator/My%20Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> [java] expected:jar:file:/C:/Documents and
>>>>>>>> Settings/Administrator/My
>>>>>>>> Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> [java] at
>>>>>>>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.testCase(Unknown
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Source)
>>>>>>>> [java] at
>>>>>>>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.run(Unknown
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Source)
>>>>>>>> [java] at com.sun.jini.qa.harness.MasterTest.doTest(Unknown
>>>>>>>> Source)
>>>>>>>> [java] at com.sun.jini.qa.harness.MasterTest.main(Unknown Source)
>>>>>>>>
>>>>>>>> The expected URL leaves the spaces as spaces. The returned URL has
>>>>>>>> the
>>>>>>>> spaces replaced, as is normal inside a URL, by %20.
>>>>>>>>
>>>>>>>> Patricia
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
Re: QA tests and spaces in file names
Posted by Peter Firmstone <ji...@zeus.net.au>.
It appears as though it can't see the jar archives in the directory:
C;\apache\river\jtsk\trunk\lib\
The missing class is from jsk-platform.jar
Did you run ant all.build first?
Cheers,
Peter.
Patricia Shanahan wrote:
> Sure:
>
> http://www.patriciashanahan.com/apache/myJTREGLog.txt
>
> Patricia
>
>
> On 7/9/2010 7:59 PM, Peter Firmstone wrote:
>> Can you dump the output to a text file and submit it?
>>
>> Peter.
>>
>> Patricia Shanahan wrote:
>>> I tried that. It didn't seem to make any difference.
>>>
>>> Patricia
>>>
>>>
>>> On 7/9/2010 4:48 PM, Peter Firmstone wrote:
>>>> Try copying your existing build.properties file to the qa directory,
>>>> just for now.
>>>>
>>>> Then try the jtreg tests again too.
>>>>
>>>> Cheers,
>>>>
>>>> Peter.
>>>>
>>>> Patricia Shanahan wrote:
>>>>> The problem seems to be a classpath issue when compiling the tests. I
>>>>> get messages of the form:
>>>>>
>>>>> C:\\apache\\river\\jtsk\\trunk\\qa\\jtreg\\com\\sun\\jini\\action\\catchSecurityException\\CatchSecurityException.java:30:
>>>>>
>>>>>
>>>>> package com.sun.jini.action does not exist
>>>>> import com.sun.jini.action.GetBooleanAction;
>>>>>
>>>>> Do I need another build.properties file in the qa directory? If so,
>>>>> what should it contain?
>>>>>
>>>>> Patricia
>>>>>
>>>>>
>>>>>
>>>>> On 7/9/2010 4:04 AM, Peter Firmstone wrote:
>>>>>> Have you tried the jtreg tests?
>>>>>>
>>>>>> The results of the jtreg tests will appear under trunk/qa/jtreg
>>>>>>
>>>>>> jtreg constructs a web page index with detailed result pages for
>>>>>> failed
>>>>>> tests.
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> Peter.
>>>>>>
>>>>>> Patricia Shanahan wrote:
>>>>>>> On of the simplifying steps I took to try to set up River
>>>>>>> development
>>>>>>> on a Windows box was use of a space-free path. I have since
>>>>>>> retested
>>>>>>> under "My Documents" and get QA test failures of the form:
>>>>>>>
>>>>>>> [java] com.sun.jini.qa.harness.TestException:
>>>>>>> [java]
>>>>>>> getResource(com/sun/jini/test/spec/loader/util/resources/files/file02)
>>>>>>>
>>>>>>>
>>>>>>> [java]
>>>>>>> returned:jar:file:/C:/Documents%20and%20Settings/Administrator/My%20Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> [java] expected:jar:file:/C:/Documents and
>>>>>>> Settings/Administrator/My
>>>>>>> Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> [java] at
>>>>>>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.testCase(Unknown
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Source)
>>>>>>> [java] at
>>>>>>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.run(Unknown
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Source)
>>>>>>> [java] at com.sun.jini.qa.harness.MasterTest.doTest(Unknown Source)
>>>>>>> [java] at com.sun.jini.qa.harness.MasterTest.main(Unknown Source)
>>>>>>>
>>>>>>> The expected URL leaves the spaces as spaces. The returned URL has
>>>>>>> the
>>>>>>> spaces replaced, as is normal inside a URL, by %20.
>>>>>>>
>>>>>>> Patricia
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
Re: QA tests and spaces in file names
Posted by Patricia Shanahan <pa...@acm.org>.
Sure:
http://www.patriciashanahan.com/apache/myJTREGLog.txt
Patricia
On 7/9/2010 7:59 PM, Peter Firmstone wrote:
> Can you dump the output to a text file and submit it?
>
> Peter.
>
> Patricia Shanahan wrote:
>> I tried that. It didn't seem to make any difference.
>>
>> Patricia
>>
>>
>> On 7/9/2010 4:48 PM, Peter Firmstone wrote:
>>> Try copying your existing build.properties file to the qa directory,
>>> just for now.
>>>
>>> Then try the jtreg tests again too.
>>>
>>> Cheers,
>>>
>>> Peter.
>>>
>>> Patricia Shanahan wrote:
>>>> The problem seems to be a classpath issue when compiling the tests. I
>>>> get messages of the form:
>>>>
>>>> C:\\apache\\river\\jtsk\\trunk\\qa\\jtreg\\com\\sun\\jini\\action\\catchSecurityException\\CatchSecurityException.java:30:
>>>>
>>>> package com.sun.jini.action does not exist
>>>> import com.sun.jini.action.GetBooleanAction;
>>>>
>>>> Do I need another build.properties file in the qa directory? If so,
>>>> what should it contain?
>>>>
>>>> Patricia
>>>>
>>>>
>>>>
>>>> On 7/9/2010 4:04 AM, Peter Firmstone wrote:
>>>>> Have you tried the jtreg tests?
>>>>>
>>>>> The results of the jtreg tests will appear under trunk/qa/jtreg
>>>>>
>>>>> jtreg constructs a web page index with detailed result pages for
>>>>> failed
>>>>> tests.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Peter.
>>>>>
>>>>> Patricia Shanahan wrote:
>>>>>> On of the simplifying steps I took to try to set up River development
>>>>>> on a Windows box was use of a space-free path. I have since retested
>>>>>> under "My Documents" and get QA test failures of the form:
>>>>>>
>>>>>> [java] com.sun.jini.qa.harness.TestException:
>>>>>> [java]
>>>>>> getResource(com/sun/jini/test/spec/loader/util/resources/files/file02)
>>>>>>
>>>>>> [java]
>>>>>> returned:jar:file:/C:/Documents%20and%20Settings/Administrator/My%20Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>>>>>
>>>>>>
>>>>>>
>>>>>> [java] expected:jar:file:/C:/Documents and Settings/Administrator/My
>>>>>> Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>>>>>
>>>>>>
>>>>>>
>>>>>> [java] at
>>>>>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.testCase(Unknown
>>>>>>
>>>>>>
>>>>>> Source)
>>>>>> [java] at
>>>>>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.run(Unknown
>>>>>>
>>>>>>
>>>>>> Source)
>>>>>> [java] at com.sun.jini.qa.harness.MasterTest.doTest(Unknown Source)
>>>>>> [java] at com.sun.jini.qa.harness.MasterTest.main(Unknown Source)
>>>>>>
>>>>>> The expected URL leaves the spaces as spaces. The returned URL has
>>>>>> the
>>>>>> spaces replaced, as is normal inside a URL, by %20.
>>>>>>
>>>>>> Patricia
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
Re: QA tests and spaces in file names
Posted by Peter Firmstone <ji...@zeus.net.au>.
Can you dump the output to a text file and submit it?
Peter.
Patricia Shanahan wrote:
> I tried that. It didn't seem to make any difference.
>
> Patricia
>
>
> On 7/9/2010 4:48 PM, Peter Firmstone wrote:
>> Try copying your existing build.properties file to the qa directory,
>> just for now.
>>
>> Then try the jtreg tests again too.
>>
>> Cheers,
>>
>> Peter.
>>
>> Patricia Shanahan wrote:
>>> The problem seems to be a classpath issue when compiling the tests. I
>>> get messages of the form:
>>>
>>> C:\\apache\\river\\jtsk\\trunk\\qa\\jtreg\\com\\sun\\jini\\action\\catchSecurityException\\CatchSecurityException.java:30:
>>>
>>> package com.sun.jini.action does not exist
>>> import com.sun.jini.action.GetBooleanAction;
>>>
>>> Do I need another build.properties file in the qa directory? If so,
>>> what should it contain?
>>>
>>> Patricia
>>>
>>>
>>>
>>> On 7/9/2010 4:04 AM, Peter Firmstone wrote:
>>>> Have you tried the jtreg tests?
>>>>
>>>> The results of the jtreg tests will appear under trunk/qa/jtreg
>>>>
>>>> jtreg constructs a web page index with detailed result pages for
>>>> failed
>>>> tests.
>>>>
>>>> Cheers,
>>>>
>>>> Peter.
>>>>
>>>> Patricia Shanahan wrote:
>>>>> On of the simplifying steps I took to try to set up River development
>>>>> on a Windows box was use of a space-free path. I have since retested
>>>>> under "My Documents" and get QA test failures of the form:
>>>>>
>>>>> [java] com.sun.jini.qa.harness.TestException:
>>>>> [java]
>>>>> getResource(com/sun/jini/test/spec/loader/util/resources/files/file02)
>>>>>
>>>>> [java]
>>>>> returned:jar:file:/C:/Documents%20and%20Settings/Administrator/My%20Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>>>>
>>>>>
>>>>>
>>>>> [java] expected:jar:file:/C:/Documents and Settings/Administrator/My
>>>>> Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>>>>
>>>>>
>>>>>
>>>>> [java] at
>>>>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.testCase(Unknown
>>>>>
>>>>>
>>>>> Source)
>>>>> [java] at
>>>>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.run(Unknown
>>>>>
>>>>>
>>>>> Source)
>>>>> [java] at com.sun.jini.qa.harness.MasterTest.doTest(Unknown Source)
>>>>> [java] at com.sun.jini.qa.harness.MasterTest.main(Unknown Source)
>>>>>
>>>>> The expected URL leaves the spaces as spaces. The returned URL has
>>>>> the
>>>>> spaces replaced, as is normal inside a URL, by %20.
>>>>>
>>>>> Patricia
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
Re: QA tests and spaces in file names
Posted by Patricia Shanahan <pa...@acm.org>.
I tried that. It didn't seem to make any difference.
Patricia
On 7/9/2010 4:48 PM, Peter Firmstone wrote:
> Try copying your existing build.properties file to the qa directory,
> just for now.
>
> Then try the jtreg tests again too.
>
> Cheers,
>
> Peter.
>
> Patricia Shanahan wrote:
>> The problem seems to be a classpath issue when compiling the tests. I
>> get messages of the form:
>>
>> C:\\apache\\river\\jtsk\\trunk\\qa\\jtreg\\com\\sun\\jini\\action\\catchSecurityException\\CatchSecurityException.java:30:
>> package com.sun.jini.action does not exist
>> import com.sun.jini.action.GetBooleanAction;
>>
>> Do I need another build.properties file in the qa directory? If so,
>> what should it contain?
>>
>> Patricia
>>
>>
>>
>> On 7/9/2010 4:04 AM, Peter Firmstone wrote:
>>> Have you tried the jtreg tests?
>>>
>>> The results of the jtreg tests will appear under trunk/qa/jtreg
>>>
>>> jtreg constructs a web page index with detailed result pages for failed
>>> tests.
>>>
>>> Cheers,
>>>
>>> Peter.
>>>
>>> Patricia Shanahan wrote:
>>>> On of the simplifying steps I took to try to set up River development
>>>> on a Windows box was use of a space-free path. I have since retested
>>>> under "My Documents" and get QA test failures of the form:
>>>>
>>>> [java] com.sun.jini.qa.harness.TestException:
>>>> [java]
>>>> getResource(com/sun/jini/test/spec/loader/util/resources/files/file02)
>>>> [java]
>>>> returned:jar:file:/C:/Documents%20and%20Settings/Administrator/My%20Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>>>
>>>>
>>>> [java] expected:jar:file:/C:/Documents and Settings/Administrator/My
>>>> Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>>>
>>>>
>>>> [java] at
>>>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.testCase(Unknown
>>>>
>>>> Source)
>>>> [java] at
>>>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.run(Unknown
>>>>
>>>> Source)
>>>> [java] at com.sun.jini.qa.harness.MasterTest.doTest(Unknown Source)
>>>> [java] at com.sun.jini.qa.harness.MasterTest.main(Unknown Source)
>>>>
>>>> The expected URL leaves the spaces as spaces. The returned URL has the
>>>> spaces replaced, as is normal inside a URL, by %20.
>>>>
>>>> Patricia
>>>>
>>>
>>>
>>
>>
>
>
Re: QA tests and spaces in file names
Posted by Peter Firmstone <ji...@zeus.net.au>.
Try copying your existing build.properties file to the qa directory,
just for now.
Then try the jtreg tests again too.
Cheers,
Peter.
Patricia Shanahan wrote:
> The problem seems to be a classpath issue when compiling the tests. I
> get messages of the form:
>
> C:\\apache\\river\\jtsk\\trunk\\qa\\jtreg\\com\\sun\\jini\\action\\catchSecurityException\\CatchSecurityException.java:30:
> package com.sun.jini.action does not exist
> import com.sun.jini.action.GetBooleanAction;
>
> Do I need another build.properties file in the qa directory? If so,
> what should it contain?
>
> Patricia
>
>
>
> On 7/9/2010 4:04 AM, Peter Firmstone wrote:
>> Have you tried the jtreg tests?
>>
>> The results of the jtreg tests will appear under trunk/qa/jtreg
>>
>> jtreg constructs a web page index with detailed result pages for failed
>> tests.
>>
>> Cheers,
>>
>> Peter.
>>
>> Patricia Shanahan wrote:
>>> On of the simplifying steps I took to try to set up River development
>>> on a Windows box was use of a space-free path. I have since retested
>>> under "My Documents" and get QA test failures of the form:
>>>
>>> [java] com.sun.jini.qa.harness.TestException:
>>> [java]
>>> getResource(com/sun/jini/test/spec/loader/util/resources/files/file02)
>>> [java]
>>> returned:jar:file:/C:/Documents%20and%20Settings/Administrator/My%20Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>>
>>>
>>> [java] expected:jar:file:/C:/Documents and Settings/Administrator/My
>>> Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>>
>>>
>>> [java] at
>>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.testCase(Unknown
>>>
>>> Source)
>>> [java] at
>>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.run(Unknown
>>>
>>> Source)
>>> [java] at com.sun.jini.qa.harness.MasterTest.doTest(Unknown Source)
>>> [java] at com.sun.jini.qa.harness.MasterTest.main(Unknown Source)
>>>
>>> The expected URL leaves the spaces as spaces. The returned URL has the
>>> spaces replaced, as is normal inside a URL, by %20.
>>>
>>> Patricia
>>>
>>
>>
>
>
Re: QA tests and spaces in file names
Posted by Patricia Shanahan <pa...@acm.org>.
The problem seems to be a classpath issue when compiling the tests. I
get messages of the form:
C:\\apache\\river\\jtsk\\trunk\\qa\\jtreg\\com\\sun\\jini\\action\\catchSecurityException\\CatchSecurityException.java:30:
package com.sun.jini.action does not exist
import com.sun.jini.action.GetBooleanAction;
Do I need another build.properties file in the qa directory? If so, what
should it contain?
Patricia
On 7/9/2010 4:04 AM, Peter Firmstone wrote:
> Have you tried the jtreg tests?
>
> The results of the jtreg tests will appear under trunk/qa/jtreg
>
> jtreg constructs a web page index with detailed result pages for failed
> tests.
>
> Cheers,
>
> Peter.
>
> Patricia Shanahan wrote:
>> On of the simplifying steps I took to try to set up River development
>> on a Windows box was use of a space-free path. I have since retested
>> under "My Documents" and get QA test failures of the form:
>>
>> [java] com.sun.jini.qa.harness.TestException:
>> [java]
>> getResource(com/sun/jini/test/spec/loader/util/resources/files/file02)
>> [java]
>> returned:jar:file:/C:/Documents%20and%20Settings/Administrator/My%20Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>
>> [java] expected:jar:file:/C:/Documents and Settings/Administrator/My
>> Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>
>> [java] at
>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.testCase(Unknown
>> Source)
>> [java] at
>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.run(Unknown
>> Source)
>> [java] at com.sun.jini.qa.harness.MasterTest.doTest(Unknown Source)
>> [java] at com.sun.jini.qa.harness.MasterTest.main(Unknown Source)
>>
>> The expected URL leaves the spaces as spaces. The returned URL has the
>> spaces replaced, as is normal inside a URL, by %20.
>>
>> Patricia
>>
>
>
Re: QA tests and spaces in file names
Posted by Patricia Shanahan <pa...@acm.org>.
I've tried, without much success, as far as I can tell. 138 out of 138
tests failed last time.
On 7/9/2010 4:04 AM, Peter Firmstone wrote:
> Have you tried the jtreg tests?
>
> The results of the jtreg tests will appear under trunk/qa/jtreg
>
> jtreg constructs a web page index with detailed result pages for failed
> tests.
>
> Cheers,
>
> Peter.
>
> Patricia Shanahan wrote:
>> On of the simplifying steps I took to try to set up River development
>> on a Windows box was use of a space-free path. I have since retested
>> under "My Documents" and get QA test failures of the form:
>>
>> [java] com.sun.jini.qa.harness.TestException:
>> [java]
>> getResource(com/sun/jini/test/spec/loader/util/resources/files/file02)
>> [java]
>> returned:jar:file:/C:/Documents%20and%20Settings/Administrator/My%20Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>
>> [java] expected:jar:file:/C:/Documents and Settings/Administrator/My
>> Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>
>> [java] at
>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.testCase(Unknown
>> Source)
>> [java] at
>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.run(Unknown
>> Source)
>> [java] at com.sun.jini.qa.harness.MasterTest.doTest(Unknown Source)
>> [java] at com.sun.jini.qa.harness.MasterTest.main(Unknown Source)
>>
>> The expected URL leaves the spaces as spaces. The returned URL has the
>> spaces replaced, as is normal inside a URL, by %20.
>>
>> Patricia
>>
>
>
Re: QA tests and spaces in file names
Posted by Peter Firmstone <ji...@zeus.net.au>.
Have you tried the jtreg tests?
The results of the jtreg tests will appear under trunk/qa/jtreg
jtreg constructs a web page index with detailed result pages for failed
tests.
Cheers,
Peter.
Patricia Shanahan wrote:
> On of the simplifying steps I took to try to set up River development
> on a Windows box was use of a space-free path. I have since retested
> under "My Documents" and get QA test failures of the form:
>
> [java] com.sun.jini.qa.harness.TestException:
> [java]
> getResource(com/sun/jini/test/spec/loader/util/resources/files/file02)
> [java]
> returned:jar:file:/C:/Documents%20and%20Settings/Administrator/My%20Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>
> [java] expected:jar:file:/C:/Documents and
> Settings/Administrator/My
> Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>
> [java] at
> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.testCase(Unknown
> Source)
> [java] at
> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.run(Unknown
> Source)
> [java] at com.sun.jini.qa.harness.MasterTest.doTest(Unknown
> Source)
> [java] at com.sun.jini.qa.harness.MasterTest.main(Unknown
> Source)
>
> The expected URL leaves the spaces as spaces. The returned URL has the
> spaces replaced, as is normal inside a URL, by %20.
>
> Patricia
>
Re: QA tests and spaces in file names
Posted by Patricia Shanahan <pa...@acm.org>.
I'm getting 35 failures with spaces in the file name, 1 without. The
failures have several different forms, but I suspect most of them come
down to constructing a URL from a file path without going through the
special character quoting step.
I've uploaded the output from the test to
http://www.patriciashanahan.com/apache/myQALog.txt
Patricia
On 7/9/2010 4:01 AM, Peter Firmstone wrote:
> Looks like the test needs to be updated to handle URL's with spaces.
> How many tests fail with spaces in file paths?
>
> Patricia Shanahan wrote:
>> On of the simplifying steps I took to try to set up River development
>> on a Windows box was use of a space-free path. I have since retested
>> under "My Documents" and get QA test failures of the form:
>>
>> [java] com.sun.jini.qa.harness.TestException:
>> [java]
>> getResource(com/sun/jini/test/spec/loader/util/resources/files/file02)
>> [java]
>> returned:jar:file:/C:/Documents%20and%20Settings/Administrator/My%20Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>
>> [java] expected:jar:file:/C:/Documents and Settings/Administrator/My
>> Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>>
>> [java] at
>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.testCase(Unknown
>> Source)
>> [java] at
>> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.run(Unknown
>> Source)
>> [java] at com.sun.jini.qa.harness.MasterTest.doTest(Unknown Source)
>> [java] at com.sun.jini.qa.harness.MasterTest.main(Unknown Source)
>>
>> The expected URL leaves the spaces as spaces. The returned URL has the
>> spaces replaced, as is normal inside a URL, by %20.
>>
>> Patricia
>>
>
>
Re: QA tests and spaces in file names
Posted by Peter Firmstone <ji...@zeus.net.au>.
Looks like the test needs to be updated to handle URL's with spaces.
How many tests fail with spaces in file paths?
Patricia Shanahan wrote:
> On of the simplifying steps I took to try to set up River development
> on a Windows box was use of a space-free path. I have since retested
> under "My Documents" and get QA test failures of the form:
>
> [java] com.sun.jini.qa.harness.TestException:
> [java]
> getResource(com/sun/jini/test/spec/loader/util/resources/files/file02)
> [java]
> returned:jar:file:/C:/Documents%20and%20Settings/Administrator/My%20Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>
> [java] expected:jar:file:/C:/Documents and
> Settings/Administrator/My
> Documents/apache_development/checkout/jtsk/trunk/qa/lib/jinitests.jar!/com/sun/jini/test/spec/loader/util/resources/files/file02
>
> [java] at
> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.testCase(Unknown
> Source)
> [java] at
> com.sun.jini.test.spec.loader.pref.preferredClassLoader.GetResources.run(Unknown
> Source)
> [java] at com.sun.jini.qa.harness.MasterTest.doTest(Unknown
> Source)
> [java] at com.sun.jini.qa.harness.MasterTest.main(Unknown
> Source)
>
> The expected URL leaves the spaces as spaces. The returned URL has the
> spaces replaced, as is normal inside a URL, by %20.
>
> Patricia
>