Ned Konz wrote:
Image version 4689.
I tried running the ModuleStorageTests, and all of them error out: 47 run, 0 passed, 0 failed, 47 errors
Is there some initialization that is required but not being done?
I explicitly tried this after updating and it all went fine for me. Does anyone else see this? A Mac/Win issue perhaps?
Henrik
On Thu, Jan 31, 2002 at 05:28:21PM +0000, Henrik Gedenryd wrote:
Ned Konz wrote:
Image version 4689.
I tried running the ModuleStorageTests, and all of them error out: 47 run, 0 passed, 0 failed, 47 errors
Is there some initialization that is required but not being done?
Same for me, no one passe... Seems to be a pb with homeModule
On Thursday 31 January 2002 09:28 am, Henrik Gedenryd wrote:
Ned Konz wrote:
Image version 4689.
I tried running the ModuleStorageTests, and all of them error out: 47 run, 0 passed, 0 failed, 47 errors
Is there some initialization that is required but not being done?
I explicitly tried this after updating and it all went fine for me. Does anyone else see this? A Mac/Win issue perhaps?
I downloaded the 4689 image from st.cs.uiuc.edu and tried it, rather than updating.
I explicitly tried this after updating and it all went fine for me. Does anyone else see this? A Mac/Win issue perhaps?
No. It's just an issue of incorrect setup for the test cases. If there isn't a root repository some of the setUp code is failing and raising errors which triggers the unit tests to fail. The behavior can be seen once you delete the root repository (I think it's in the VM directory), then change ModuleStorageTests>>setUp into
setUp ^[super setUp] on: Error do:[:ex| self halt: 'oops'].
That will show you an InvalidDirectoryError. So I think setUp should really create this directory. BTW, it seems strange to me that ModuleTests>>setUp is implemented as "self tearDown"....
Cheers, - Andreas
squeak-dev@lists.squeakfoundation.org