On Wed, Nov 18, 2009 at 09:44:08PM -0500, David T. Lewis wrote:
> On Wed, Nov 18, 2009 at 05:14:04PM -0500, David T. Lewis wrote:
> > On Wed, Nov 18, 2009 at 08:55:50AM -0500, Schwab,Wilhelm K wrote:
> > > Dave,
> > > 
> > > It would help to knock the MVC workspace out of the offending #initialize
> > > method and re-save the packages.  In my experience, that simple change 
> > > make
> > > the load hassle-free vs. the current situation.
> > 
> > Bill,
> > 
> > Good idea, thanks. I'll take a look at that when I get home.
> 
> Well actually there were not any MVC references in #initialize. But
> CommandShell class>>initialize opens a shell window, and that was failing
> because text style 'Atlanta' no longer exists in Pharo. I fixed this,
> so if you update to CommandShell-dtl.40.mcz that failure will no longer
> occur. The shell window does not actually work, but at least the window
> opens properly now. One bug down, ??? to go ...

Correction, the shell window *does* seem to be working, so this is
actually looking much better now. However, the CommandShellTestCase
does not pass (hangs up part way through, lots of zombie unix processes
left unhandled).

The other unit tests are passing, with the exception of the tests in
AioEventHandlerTestCase that use sockets. This is due to changes in
the socket support in Pharo, but I am not worried about these failures
as they probably just require updates to the tests to match the
Pharo socket support.

I am testing on Linux with a VM that I built locally. For OS X, an
updated OSProcessPlugin will need to be included with the VM, otherwise
we will have VM crashes when handling external process exit.

The main concerns now are:

1) Need an updated OSProcessPlugin for the Mac VM (for both Squeak and Pharo)

2) Why does CommandShellTestCase on Pharo get hung up and leave zombies?

Note, CommandShellTestCase is a real stress test for OSProcess. It does
a lot of concurrent process handling with pipelines of OS processes
interacting with Squeak/Pharo. If this test does not pass, then I am
not confident in the overall reliability of OSProcess.

Dave
 

_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to