<div dir="ltr"><font color="#330033"><font size="2"><font face="tahoma,sans-serif">Dale,<br>Please use the following for the build process:<br>WAConfiguration allInstancesDo: [ :instance | instance clearSearchContexts ].<br>
WAConfiguration allSubInstancesDo: [ :instance | instance clearSearchContexts ].<br><br>After running these the tests seem to clear.<br>We will continue discussion on issue 643 on the issues tracker.</font></font></font><div style="margin: 2em 0pt;" name="sig_83fa755cf9">
Cheers,<br>
Avi.</div><div class="gmail_quote">On Fri, Feb 11, 2011 at 11:35 PM, Dale Henrichs <span dir="ltr"><<a href="mailto:dhenrich@vmware.com">dhenrich@vmware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
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 ...<br><font color="#888888">
<br>
<br>
Dale</font><div><div></div><div class="h5"><br>
<br>
On 02/11/2011 09:58 AM, Dale Henrichs wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
On 02/09/2011 05:49 PM, Dale Henrichs wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
PharoCore1.0:<br>
<br>
- WAHtmlFileHandlerListingTest>>testFileLibraries results in a<br>
WAAttributeNotFound being signalled (test error). I'll dig into this<br>
one a little bit more tomorrow.<br>
</blockquote>
<br>
I've done a little poking around this test failure and I discovered that<br>
if I reach in the instance of WaConfiguration where the test was failing<br>
and niled out the cachedSearchContexts instance variable, all of the<br>
tests pass from here on out ... so somewhere, somehow a bad search<br>
context got cached ...<br>
<br>
This makes me wonder if the problem just happened to appear in<br>
PharoCore1.0 and is an indication of potential issues on other platforms<br>
... or ... there really is something in PharoCore1.0 that is the source<br>
of this bug?<br>
<br>
Dale<br>
_______________________________________________<br>
seaside-dev mailing list<br>
<a href="mailto:seaside-dev@lists.squeakfoundation.org" target="_blank">seaside-dev@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev" target="_blank">http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev</a><br>
</blockquote>
<br>
<br>
_______________________________________________<br>
seaside-dev mailing list<br>
<a href="mailto:seaside-dev@lists.squeakfoundation.org" target="_blank">seaside-dev@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev" target="_blank">http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev</a><br>
</div></div></blockquote></div><br></div>