Maybe cc'ing VM mailing list can help.<br><br><div class="gmail_quote">On Fri, Jul 1, 2011 at 9:32 AM, Lukas Renggli <span dir="ltr"><<a href="mailto:renggli@gmail.com">renggli@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi Eliot,<br>
<br>
I am using one of the latest VMs from your site (VM.r2434) and I<br>
continue to have subtle problems with objects as methods (#flushCache,<br>
#run:with:in:).<br>
<br>
The issue is that the test coverage in Pharo is kind of broken on Cog<br>
for a long time already. It reports methods as not covered that are<br>
clearly covered, and tests seem to randomly fail.<br>
<br>
I suspected that there is something wrong with the coverage code<br>
itself. So I started to experiment with TestCoverage>>flushCache and<br>
noticed that the current implementation<br>
<br>
TestCoverage>>flushCache<br>
self reference methodSymbol flushCache<br>
<br>
performs not that well: The set of not covered methods is wrong and<br>
many tests suddenly fail. If I replace it with<br>
<br>
TestCoverage>>flushCache<br>
self reference actualClass flushCache<br>
<br>
I actually get accurate coverage information, but there are still a<br>
few tests constantly failing. I tried to use all possible combinations<br>
of #flushCache (also calling it on the compiled method), but only<br>
flushing the cache on the class seems to work properly. So far so<br>
good, but I really wonder what the correct way is to flush the cache?<br>
:-)<br>
<br>
For my experiments I was using the package 'AST-Tests-Semantics'. This<br>
is a small package with lots of test methods that cover each method<br>
but one (RBSemanticAnnotationMisssing>>#isResumable). Now the "real"<br>
problem is that when running these tests in coverage mode, the same 4<br>
tests always fail:<br>
<br>
RBSemanticTest>>testBlockScope<br>
RBSemanticTest>>testCascadeReceiver<br>
RBSemanticTest>>testClassVariableBinding<br>
RBSemanticTest>>testGlobalVariableBinding<br>
<br>
Not sure of how to debug that? Do you have an idea why these otherwise<br>
passing tests suddenly fail? If you want to try to reproduce you can<br>
use any Pharo image with the tests loaded, or use those that I used:<br>
<br>
<a href="http://jenkins.lukas-renggli.ch/job/Development/lastSuccessfulBuild/artifact/omnibrowser-tests/omnibrowser-tests.changes" target="_blank">http://jenkins.lukas-renggli.ch/job/Development/lastSuccessfulBuild/artifact/omnibrowser-tests/omnibrowser-tests.changes</a><br>
<a href="http://jenkins.lukas-renggli.ch/job/Development/lastSuccessfulBuild/artifact/omnibrowser-tests/omnibrowser-tests.image" target="_blank">http://jenkins.lukas-renggli.ch/job/Development/lastSuccessfulBuild/artifact/omnibrowser-tests/omnibrowser-tests.image</a><br>
<br>
Open the Test Runner, select 'AST-Tests-Semantics' and 'Run Coverage'.<br>
<br>
Any help or clarification would be appreciated :-)<br>
<br>
Lukas<br>
<font color="#888888"><br>
--<br>
Lukas Renggli<br>
<a href="http://www.lukas-renggli.ch" target="_blank">www.lukas-renggli.ch</a><br>
<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Mariano<br><a href="http://marianopeck.wordpress.com" target="_blank">http://marianopeck.wordpress.com</a><br><br>