You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Dag H. Wanvik (JIRA)" <de...@db.apache.org> on 2005/05/25 00:35:54 UTC
[jira] Created: (DERBY-313) testing/README.htm describes non-existing property
testing/README.htm describes non-existing property
--------------------------------------------------
Key: DERBY-313
URL: http://issues.apache.org/jira/browse/DERBY-313
Project: Derby
Type: Bug
Components: Documentation
Versions: 10.1.0.0
Environment: n/a
Reporter: Dag H. Wanvik
Priority: Minor
In section 4.12 in ../testing/README.htm, the property
TestSpecialFlags
is described for specifying additional properties to RunTest. I could not
find any evidence of this in RunTest or elsewhere. However, the property
testSpecialProps
is supported by RunTest.java. I found this to work. This property
also has a syntax for specifying more than one property using a "^"
delimiter between properties, i.e.
testSpecialProps=<prop-1>=<value-1>^ ... ^<prop-n>=<value-n>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Re: [jira] Commented: (DERBY-313) testing/README.htm describes
non-existing property
Posted by "Dag H. Wanvik" <Da...@Sun.COM>.
Hi,
>>>>> "MvL" == Myrna van Lunteren <m....@gmail.com> wrote:
MvL> RunTest.java is not entirely consistent in the comments relating to this,
MvL> and in 2 places it actually says testSpecialFlags. Maybe you can correct
MvL> those comments in RunTest too? It should either say SpecialFlags, or
MvL> testSpecialProps.
MvL> (there's on one line 1324:
MvL> ' // If app props are still empty, check for any special testSpecialFlags'
MvL> and on 1332:
MvL> '// merge any special properties from testSpecialFlags')
Yes, I will fix RunTest, too :)
Thanks,
Dag
[PATCH] (DERBY-313) testing/README.htm describes non-existing property
Posted by "Dag H. Wanvik" <Da...@Sun.COM>.
Just uploaded a patch for this, comments are in the JIRA issue.
http://issues.apache.org/jira/browse/DERBY-313
Dag
Re: [jira] Commented: (DERBY-313) testing/README.htm describes non-existing property
Posted by Myrna van Lunteren <m....@gmail.com>.
>On 5/25/05, Dag H. Wanvik (JIRA) commented on DERBY-313:
>-------------------------------------
>Unless sombody yells, I will make a patch reflecting this finding. Yell now
;-)
No, you are absolutely right. My error in writing the doc.
SpecialFlags is a class in the harness, which parses the testSpecialProps
property.
RunTest.java is not entirely consistent in the comments relating to this,
and in 2 places it actually says testSpecialFlags. Maybe you can correct
those comments in RunTest too? It should either say SpecialFlags, or
testSpecialProps.
(there's on one line 1324:
' // If app props are still empty, check for any special testSpecialFlags'
and on 1332:
'// merge any special properties from testSpecialFlags')
> --------------------------------------------------
>> In section 4.12 in ../testing/README.htm, the property
> TestSpecialFlags
> is described for specifying additional properties to RunTest. I could not
> find any evidence of this in RunTest or elsewhere. However, the property
> testSpecialProps
> is supported by RunTest.java. I found this to work. This property
> also has a syntax for specifying more than one property using a "^"
> delimiter between properties, i.e.
> testSpecialProps=<prop-1>=<value-1>^ ... ^<prop-n>=<value-n>
[jira] Commented: (DERBY-313) testing/README.htm describes non-existing property
Posted by "Dag H. Wanvik (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-313?page=comments#action_66476 ]
Dag H. Wanvik commented on DERBY-313:
-------------------------------------
Added a patch for this. I did the following:
- changed occurences of TestSpecialFlags to testSpecialProps in the README.thm and in
code comments in RunTest.java
- In README.htm, added explanation of how to set several properties with testSpecialProps
- fixed a typo in testSpecialProps in README.htm
Diff is uploaded, stat is:
M java/testing/README.htm
M java/testing/org/apache/derbyTesting/functionTests/harness/RunTest.java
Tests run: Since I only changed comments in the code, for sanity check I ran a single test using the modified RunTest.
> testing/README.htm describes non-existing property
> --------------------------------------------------
>
> Key: DERBY-313
> URL: http://issues.apache.org/jira/browse/DERBY-313
> Project: Derby
> Type: Bug
> Components: Documentation
> Versions: 10.1.0.0
> Environment: n/a
> Reporter: Dag H. Wanvik
> Assignee: Dag H. Wanvik
> Priority: Minor
> Attachments: 313.diff
>
> In section 4.12 in ../testing/README.htm, the property
> TestSpecialFlags
> is described for specifying additional properties to RunTest. I could not
> find any evidence of this in RunTest or elsewhere. However, the property
> testSpecialProps
> is supported by RunTest.java. I found this to work. This property
> also has a syntax for specifying more than one property using a "^"
> delimiter between properties, i.e.
> testSpecialProps=<prop-1>=<value-1>^ ... ^<prop-n>=<value-n>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-313) testing/README.htm describes non-existing property
Posted by "Dag H. Wanvik (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-313?page=comments#action_66316 ]
Dag H. Wanvik commented on DERBY-313:
-------------------------------------
Unless sombody yells, I will make a patch reflecting this finding. Yell now ;-)
> testing/README.htm describes non-existing property
> --------------------------------------------------
>
> Key: DERBY-313
> URL: http://issues.apache.org/jira/browse/DERBY-313
> Project: Derby
> Type: Bug
> Components: Documentation
> Versions: 10.1.0.0
> Environment: n/a
> Reporter: Dag H. Wanvik
> Priority: Minor
>
> In section 4.12 in ../testing/README.htm, the property
> TestSpecialFlags
> is described for specifying additional properties to RunTest. I could not
> find any evidence of this in RunTest or elsewhere. However, the property
> testSpecialProps
> is supported by RunTest.java. I found this to work. This property
> also has a syntax for specifying more than one property using a "^"
> delimiter between properties, i.e.
> testSpecialProps=<prop-1>=<value-1>^ ... ^<prop-n>=<value-n>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-313) testing/README.htm describes non-existing property
Posted by "Dag H. Wanvik (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-313?page=all ]
Dag H. Wanvik updated DERBY-313:
--------------------------------
Attachment: 313.diff
this replaces the first 313.diff; added a note on "useprocess"
> testing/README.htm describes non-existing property
> --------------------------------------------------
>
> Key: DERBY-313
> URL: http://issues.apache.org/jira/browse/DERBY-313
> Project: Derby
> Type: Bug
> Components: Documentation
> Versions: 10.1.0.0
> Environment: n/a
> Reporter: Dag H. Wanvik
> Assignee: Dag H. Wanvik
> Priority: Minor
> Attachments: 313.diff
>
> In section 4.12 in ../testing/README.htm, the property
> TestSpecialFlags
> is described for specifying additional properties to RunTest. I could not
> find any evidence of this in RunTest or elsewhere. However, the property
> testSpecialProps
> is supported by RunTest.java. I found this to work. This property
> also has a syntax for specifying more than one property using a "^"
> delimiter between properties, i.e.
> testSpecialProps=<prop-1>=<value-1>^ ... ^<prop-n>=<value-n>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-313) testing/README.htm describes non-existing property
Posted by "Dag H. Wanvik (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-313?page=all ]
Dag H. Wanvik updated DERBY-313:
--------------------------------
Attachment: 313.diff
> testing/README.htm describes non-existing property
> --------------------------------------------------
>
> Key: DERBY-313
> URL: http://issues.apache.org/jira/browse/DERBY-313
> Project: Derby
> Type: Bug
> Components: Documentation
> Versions: 10.1.0.0
> Environment: n/a
> Reporter: Dag H. Wanvik
> Assignee: Dag H. Wanvik
> Priority: Minor
> Attachments: 313.diff
>
> In section 4.12 in ../testing/README.htm, the property
> TestSpecialFlags
> is described for specifying additional properties to RunTest. I could not
> find any evidence of this in RunTest or elsewhere. However, the property
> testSpecialProps
> is supported by RunTest.java. I found this to work. This property
> also has a syntax for specifying more than one property using a "^"
> delimiter between properties, i.e.
> testSpecialProps=<prop-1>=<value-1>^ ... ^<prop-n>=<value-n>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (DERBY-313) testing/README.htm property descriptions: testSpecialProps wrongly named; useprocess omitted
Posted by "Samuel Andrew McIntyre (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-313?page=all ]
Samuel Andrew McIntyre closed DERBY-313:
----------------------------------------
Resolution: Fixed
Fix Version: 10.1.0.0
Committed, revision 179402.
> testing/README.htm property descriptions: testSpecialProps wrongly named; useprocess omitted
> --------------------------------------------------------------------------------------------
>
> Key: DERBY-313
> URL: http://issues.apache.org/jira/browse/DERBY-313
> Project: Derby
> Type: Bug
> Components: Documentation
> Versions: 10.1.0.0
> Environment: n/a
> Reporter: Dag H. Wanvik
> Assignee: Dag H. Wanvik
> Priority: Minor
> Fix For: 10.1.0.0
> Attachments: 313.diff
>
> In section 4.12 in ../testing/README.htm, the property
> TestSpecialFlags
> is described for specifying additional properties to RunTest. I could not
> find any evidence of this in RunTest or elsewhere. However, the property
> testSpecialProps
> is supported by RunTest.java. I found this to work. This property
> also has a syntax for specifying more than one property using a "^"
> delimiter between properties, i.e.
> testSpecialProps=<prop-1>=<value-1>^ ... ^<prop-n>=<value-n>
> Also,I noticed the property "useprocess" (default=true) for controlling
> whether RunTest runs the test in a separate vm or a thread in current
> vm isn't documented in README.htm. I suggest it be included, since
> it's potentially useful for debugging tests. I could include it in the
> patch for derby-313 (I don't think anybody committed it yet) or file a
> new JIRA issue.
> Looking at RunTest reveals that unit tests are not (yet) runnable with
> "useprocess=false", though.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Assigned: (DERBY-313) testing/README.htm describes non-existing property
Posted by "Dag H. Wanvik (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-313?page=all ]
Dag H. Wanvik reassigned DERBY-313:
-----------------------------------
Assign To: Dag H. Wanvik
> testing/README.htm describes non-existing property
> --------------------------------------------------
>
> Key: DERBY-313
> URL: http://issues.apache.org/jira/browse/DERBY-313
> Project: Derby
> Type: Bug
> Components: Documentation
> Versions: 10.1.0.0
> Environment: n/a
> Reporter: Dag H. Wanvik
> Assignee: Dag H. Wanvik
> Priority: Minor
>
> In section 4.12 in ../testing/README.htm, the property
> TestSpecialFlags
> is described for specifying additional properties to RunTest. I could not
> find any evidence of this in RunTest or elsewhere. However, the property
> testSpecialProps
> is supported by RunTest.java. I found this to work. This property
> also has a syntax for specifying more than one property using a "^"
> delimiter between properties, i.e.
> testSpecialProps=<prop-1>=<value-1>^ ... ^<prop-n>=<value-n>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-313) testing/README.htm property descriptions: testSpecialProps wrongly named; useprocess omitted
Posted by "Dag H. Wanvik (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-313?page=all ]
Dag H. Wanvik updated DERBY-313:
--------------------------------
Summary: testing/README.htm property descriptions: testSpecialProps wrongly named; useprocess omitted (was: testing/README.htm describes non-existing property)
Description:
In section 4.12 in ../testing/README.htm, the property
TestSpecialFlags
is described for specifying additional properties to RunTest. I could not
find any evidence of this in RunTest or elsewhere. However, the property
testSpecialProps
is supported by RunTest.java. I found this to work. This property
also has a syntax for specifying more than one property using a "^"
delimiter between properties, i.e.
testSpecialProps=<prop-1>=<value-1>^ ... ^<prop-n>=<value-n>
Also,I noticed the property "useprocess" (default=true) for controlling
whether RunTest runs the test in a separate vm or a thread in current
vm isn't documented in README.htm. I suggest it be included, since
it's potentially useful for debugging tests. I could include it in the
patch for derby-313 (I don't think anybody committed it yet) or file a
new JIRA issue.
Looking at RunTest reveals that unit tests are not (yet) runnable with
"useprocess=false", though.
was:
In section 4.12 in ../testing/README.htm, the property
TestSpecialFlags
is described for specifying additional properties to RunTest. I could not
find any evidence of this in RunTest or elsewhere. However, the property
testSpecialProps
is supported by RunTest.java. I found this to work. This property
also has a syntax for specifying more than one property using a "^"
delimiter between properties, i.e.
testSpecialProps=<prop-1>=<value-1>^ ... ^<prop-n>=<value-n>
> testing/README.htm property descriptions: testSpecialProps wrongly named; useprocess omitted
> --------------------------------------------------------------------------------------------
>
> Key: DERBY-313
> URL: http://issues.apache.org/jira/browse/DERBY-313
> Project: Derby
> Type: Bug
> Components: Documentation
> Versions: 10.1.0.0
> Environment: n/a
> Reporter: Dag H. Wanvik
> Assignee: Dag H. Wanvik
> Priority: Minor
> Attachments: 313.diff
>
> In section 4.12 in ../testing/README.htm, the property
> TestSpecialFlags
> is described for specifying additional properties to RunTest. I could not
> find any evidence of this in RunTest or elsewhere. However, the property
> testSpecialProps
> is supported by RunTest.java. I found this to work. This property
> also has a syntax for specifying more than one property using a "^"
> delimiter between properties, i.e.
> testSpecialProps=<prop-1>=<value-1>^ ... ^<prop-n>=<value-n>
> Also,I noticed the property "useprocess" (default=true) for controlling
> whether RunTest runs the test in a separate vm or a thread in current
> vm isn't documented in README.htm. I suggest it be included, since
> it's potentially useful for debugging tests. I could include it in the
> patch for derby-313 (I don't think anybody committed it yet) or file a
> new JIRA issue.
> Looking at RunTest reveals that unit tests are not (yet) runnable with
> "useprocess=false", though.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira