[Seaside-dev] 3.0.4 status (PharoCore1.0)

[Avi Shefi]

Dale,
I didn't mean for those lines to be included in any method, but as an
immediate fix for the "unstable" search contexts.
Indeed clearing the search contexts solves the tests failures.
Cheers,
Avi.
On Sat, Feb 12, 2011 at 1:24 AM, Dale Henrichs <dhenrich at vmware.com> wrote:

> Avi,
>
> In GemStone it is not a good idea to rely on allInstances since a
> repository can be quite large, so I'm reluctant to put in such a method.
>
> Presumably something like the following will work:
>
>  WASystemConfiguration allSubclasses do: [ :each |
>    each instance
>        clearSearchContexts;
>        clearDescription ].
>
> without resorting to allInstances? In the particular case I've seen
> clearing the description and search context would do the trick...
>
> Dale
>
>
> On 02/11/2011 03:02 PM, Avi Shefi wrote:
>
>> Dale,
>> Please use the following for the build process:
>> WAConfiguration allInstancesDo: [ :instance | instance
>> clearSearchContexts ].
>> WAConfiguration allSubInstancesDo: [ :instance | instance
>> clearSearchContexts ].
>>
>> After running these the tests seem to clear.
>> We will continue discussion on issue 643 on the issues tracker.
>> Cheers,
>> Avi.
>> On Fri, Feb 11, 2011 at 11:35 PM, Dale Henrichs <dhenrich at vmware.com
>> <mailto:dhenrich at vmware.com>> wrote:
>>
>>    If I load latest mcz files into Pharo1.0 and run the tests they run
>>    clean ... so the problem is strictly an upgrade problem and probably
>>    exists on all platforms ...
>>
>>
>>    Dale
>>
>>
>>    On 02/11/2011 09:58 AM, Dale Henrichs wrote:
>>
>>        On 02/09/2011 05:49 PM, Dale Henrichs wrote:
>>
>>            PharoCore1.0:
>>
>>                 - WAHtmlFileHandlerListingTest>>testFileLibraries
>>            results in a
>>                   WAAttributeNotFound being signalled (test error).
>>            I'll dig into this
>>                   one a little bit more tomorrow.
>>
>>
>>        I've done a little poking around this test failure and I
>>        discovered that
>>        if I reach in the instance of WaConfiguration where the test was
>>        failing
>>        and niled out the cachedSearchContexts instance variable, all of
>> the
>>        tests pass from here on out ... so somewhere, somehow a bad search
>>        context got cached ...
>>
>>        This makes me wonder if the problem just happened to appear in
>>        PharoCore1.0 and is an indication of potential issues on other
>>        platforms
>>        ... or ... there really is something in PharoCore1.0 that is the
>>        source
>>        of this bug?
>>
>>        Dale
>>        _______________________________________________
>>        seaside-dev mailing list
>>        seaside-dev at lists.squeakfoundation.org
>>        <mailto:seaside-dev at lists.squeakfoundation.org>
>>
>>        http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>>
>>
>>
>>    _______________________________________________
>>    seaside-dev mailing list
>>    seaside-dev at lists.squeakfoundation.org
>>    <mailto:seaside-dev at lists.squeakfoundation.org>
>>
>>    http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside-dev/attachments/20110212/1c1b6db8/attachment.htm