test suite early failure on 3.10 Windows

Ross Boylan ross at biostat.ucsf.edu
Mon Nov 9 03:51:17 UTC 2009


On Sun, 2009-11-08 at 22:07 -0500, David T. Lewis wrote:
> On Sun, Nov 08, 2009 at 01:25:35PM -0800, Ross Boylan wrote:
> > On Sun, 2009-11-08 at 15:48 -0500, David T. Lewis wrote:
> > > On Sun, Nov 08, 2009 at 12:37:23PM -0800, Ross Boylan wrote:
> > > > I loaded magma into a 3.10 basic image along with OSProcess, 
> > > > NewCompiler, their dependencies and some other stuff on Linux.  I copied 
> > > > it to Windows Vista and executed
> > > > MagmaTestCase fullSuite maDebug
> > > > The image got changed to _magmaTestConductor image, but before any other 
> > > > windows were launched I got the error whose stack trace appears below.
> > > > 
> > > > The problem seems to be that in the 2nd item up the stack, 
> > > > ExternalWindowsOSProcess>>value,
> > > > self initialStdErr
> > > > returns nil.
> > > > 
> > > > Any ideas?
> > > 
> > > Ross,
> > > 
> > > OSProcess has very limited functionality on Windows, and the required
> > > plugin is not distributed with the VM. Sorry.
> > > 
> > > Dave
> > Ouch!
> > 
> > Is the plugin not distributed because it doesn't work well?
> > 
> > Is magma (as distinct from the test suite) believed to work on Windows?
> > Is there a way to run the tests with me manually launching things?
> 
> Magma is in no way dependent on OSProcess. That is just a convenience
> for setting up tests, nothing more.
> 
Yes, but that still leaves the question of whether magma is known to
work on Windows (esp Vista).  Without a way of testing it, that's hard
to tell.
Ross



More information about the Magma mailing list