This could be a problem with the coverage analysis. You have to be
extra careful with coverage analysis on system classes like
collections and filestreams, because they are used everywhere.

Lukas

On Tuesday, April 6, 2010, Stan Shepherd <stan.shepherd414@gmail.com> wrote:
>
> VM: unix - i686 - linux-gnu - Pharo0.1 of 16 May 2008 [latest update:
> #10074]
> Image: Pharo-1.0-10517-rc4 [Latest update: #10517]
>
> Steps to reproduce:
> 1.In TestRunner, select Tests-Traits , TestTraits
> 2.Select Run Coverage button.
> 3.In dialog, select Files
>
>
> �stack trace attached ** to issue **
> http://code.google.com/p/pharo/issues/detail?id=2279
> --
> View this message in context: http://n4.nabble.com/Issue-2279-BUG-MultiByteFileStream-Object-error-on-changes-file-throwing-System-Error-Handling-Failee-tp1752526p1752526.html
> Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

--
Lukas Renggli
www.lukas-renggli.ch

_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project