> I don't know why, exactly, but extend test 11 and 12 don't work on > windiws, at least under cygwin--they hang. (For a while extend 11 was > sucking down all availabe memory, which was fun) > > Is anyone else seeing this? (Heck, is anyone else trying with cygwin on > windows?) I'm tempted to disable the test for now, if for no other reason > than to get non-freezing tests so the tinders work out OK. On Win32 using nmake, cl, etc extend.t fails on test 11 (see the thread Tinderboxes). 12 is no problem.
Don't tend to test it much on cygwin, but have done it now. Of possible interest is this warning when running Configure.pl:- Determining some sizes... Hmm, I see your chosen INTVAL isn't the same size as your pointers. Parrot should still compile and run, but you may see a ton of warnings. done. You have to configure with --jitcapable=0 under cygwin just as you do with nmake/cl (see thread NCI broken on Win32 for why). Tests 11 and 12, like you say, cause big problems. 11 reached 200 MB of allocated memory before I decided enough was enough, and 12 was easily heading in the same direction. Memory allocation seems go grow linearly rather than exponentionally, but that's only from me watching a number change and judging it based on that. Jonathan
