test suite later failure Squeak 3.10 + Vista

[Ross Boylan]

I started with a clean 3.10 image and added NewCompiler and Magma
tester, but not OSProcess.  The testConductor popped up windows telling
me to launch various images manually, which I did.

Further into the test I had to relaunch one image.  I walked away, and c
30 minutes later came back.  There was no activity and the last line in
the transcript on the conductor was
"launching ..\_magmaTestserver.image".
Unlike previous times, there was no window telling me that OSProcess was
not loaded an I should launch manually.

The last few lines above the launching message in the transcript are
remote performing setSiumlateServerOutage
remote performing commitDistaster
waiting for server to shutdown (twice)
Could not connect to port 1316.

The transcript scrollbar suggests there might be a line below the last
visible line.

I launched the _magmaTestserver image manually, but nothing happened.  I
tried to manipulate the conductor, but, as had been the case throughout
the test, it was unresponsive to mouse clicks (or movement: putting the
mouse over resizing handles did not change the icon).  I tried ctl-. and
alt-.  The bottom part of my conductor window showed white with WARNING:
event buffer overflow when I moved my mouse into the area of the regular
image.  The bottom part of the window had a scrollbar; the very top of
the (white) scrolling region says
# Debug Console

It's possible the window prompting to launch the other process manually
was covered by other windows.

Also, _magamTestclient2.image has a window titled "Verify these
projects" which says to go into a bunch of projects to see if they look
ok.  Then it lists the projects, saying "not present" after each one.
It is correct: they aren't there (only the conductor image seems
unresponsive).  The projects are 
Building with Squeak
Fun with Morphic
Fun With Music
SmalltalkIntroduction

I have a couple of ideas.  First, maybe the projects are not present
because they were stripped out of 3.10.  Second, maybe the main failure
described above is the result of a long wait before I launched the
server image.