Issue 225 in glassdb: WALotsaLinksFunctionalTest still failing in GemStone 3.x

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Issue 225 in glassdb: WALotsaLinksFunctionalTest still failing in GemStone 3.x

glassdb
Status: Accepted
Owner: [hidden email]
Labels: Type-Defect Priority-Medium GLASS-Server Version-3.0.x  
Milestone-1.0-beta.8.6

New issue 225 by [hidden email]: WALotsaLinksFunctionalTest still  
failing in GemStone 3.x
http://code.google.com/p/glassdb/issues/detail?id=225

While Issue 219 has been fixed in GemStone 3.0, the  
WALotsaLinksFunctionalTest Seaside test case is still failing ...

presumably this is a problem with nested blocks in a partial continuation?



Reply | Threaded
Open this post in threaded view
|

Re: Issue 225 in glassdb: WALotsaLinksFunctionalTest still failing in GemStone 3.x

glassdb
Updates:
        Labels: bugid-38359

Comment #1 on issue 225 by [hidden email]: WALotsaLinksFunctionalTest  
still failing in GemStone 3.x
http://code.google.com/p/glassdb/issues/detail?id=225

WALotsaLinksFunctionalTest has exposed a bug in the GemStone3.0 nested  
block handling...the following test case with one more level of nesting  
behaves incorrectly:

testClosureParameters
        | closures |
        closures := OrderedCollection new.
        1 to: 5 do: [:val |
                [ closures add: [val]] value ].
       
        closures do: [:aClosure |
                Transcript show: aClosure value asString; cr ]

Keep this bug separate from Issue 219, since Issue 219 will be kept open  
for GemStone2.x and this bug marked as fixed when 3.x is fixed

Reply | Threaded
Open this post in threaded view
|

Re: Issue 225 in glassdb: WALotsaLinksFunctionalTest still failing in GemStone 3.x

glassdb
Updates:
        Status: Fixed
        Labels: Fixed-1.0-beta.8.7

Comment #2 on issue 225 by [hidden email]: WALotsaLinksFunctionalTest  
still failing in GemStone 3.x
http://code.google.com/p/glassdb/issues/detail?id=225

Verified fixed in GemStone 3.0.1 ... internal bug 38359 marked fixed on:  
05/05/11 in version: 3.0