Re: [Pharo-project] [ANN 1.3] One-Click #13315

[Ben Coman]

Pharo 1.4 works okay, which is great the crash is avoided,  but with only 8804 tests versus 9757 in Pharo 1.3 it is unclear whether: 1. Bug has been fixed in VM. 2. System Code has been removed from image 3. Test Code exercising the crash has been removed from image Ideally the problem doesn't just go away by itself :)  otherwise it might be scenario 2. or 3. above rather than 1 :) However I then reran Pharo-1.3 image with no crash - so a null experiment. For your records, I did the following... a. extracted Pharo-1.3-13315-OneClick.zip b. extracted Pharo-1.4-14210.zip into the Resource folder, c. renamed pharo.exe & pharo.ini to pharo14.exe & pharo14.ini as described in my previous report d. modified pharo14.ini with ImageFile=Contents\Resources\pharo-1.4.image e. ran pharo14.exe, opened TestRunner and clicked <Run Selected>, then later clicked <Run Selected> a second time. f. Quit g. modified pharo14.ini with ImageFile=Contents\Resources\pharo.image h. ran pharo14.exe, opened TestRunner and clicked <Run Selected> i. Quit Mariano Martinez Peck wrote: Hi. There was some crash related to network changes... but I don't remember that much. Maybe Sven can help you. Attach here the dump file and the PharoDebug.log no problem. Did you also try in pharo 1.4 ?  just to see if it works there. thanks On Sun, Oct 30, 2011 at 3:49 PM, Ben Coman <b...@openinworld.com> wrote: Ben Coman wrote: Marcus Denker wrote: Please test...    https://gforge.inria.fr/frs/download.php/29274/Pharo-1.3-13315-OneClick.zip -- Marcus Denker -- http://marcusdenker.de   I've spent the weekend trying to isolate a VM crash varying the conditions under which pharo.exe runs.  The user steps to reproduce are minimal: 1. Run pharo.exe 2. Open TestRunner 3. Click <Run Selected> ...but this leaves a lot of possibilities. I have Windows 7 and I usually operate under a non-admin account, but also did testing with an admin account.  I got the feeling the problem is network related.  During the test run a Windows Security Alert regarding the firewall blocking functionality would appear, and a fair while later the VM would crash.  It seems under a non-admin account the OS then choses to deny by default because for subsequent runs of pharo.exe, the WSA did not appear and also the image did not crash the first time <Run Selected> was clicked from TestRunner, but a second click of <Run Selected> would still crash the image. I'm not sure on the list policy of attaching a 1.7MB file with report and crash dumps, so for interested parties I have sent the file direct to Marcus. cheers, Ben btw, is there a way to match up a particular test run number with the Testcase that produced it ? -- Mariano http://marianopeck.wordpress.com