John is right. This is an important test. In my work image it works fine. That it fails in Pharo is indicative of some problem with the execution simulation machinery and closures. You're missing some changes.
BTW, in my image the class is BlockTest (see attached) 2010/3/19 John M McIntosh <john...@smalltalkconsulting.com> > Careful, does anyone understand why it works, then why it fails. > Is it because the environment changes? Or some subtle issue in blocks? > Removing it because it fails doesn't seem like a useful criteria if it's > attempted to give us a clue? > > On 2010-03-19, at 12:41 PM, Stéphane Ducasse wrote: > > > remove it! > > > > Stef > > > > On Mar 19, 2010, at 8:02 PM, Mariano Martinez Peck wrote: > > > >> > >> > >> - Make BlockContextTest>>testTrace run by commenting out broken part > >> of code simulation > >> > >> > >> Adrian: In 10515 this test sometime fails, but then running it again, it > works :( > >> > > -- > =========================================================================== > John M. McIntosh <john...@smalltalkconsulting.com> Twitter: > squeaker68882 > Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com > =========================================================================== > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project@lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >
BlockTest.st
Description: Binary data
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
