Re: [Pharo-project] where to report vm crashes? (while running Moose tests)
Esteban wrote:
Eliot builds will always have the old vm warning, even if they are not old :)... you need one of the pharo builds (CogVM, NBCogVM or PharoVM)
Well, Doru reported they crashed. Eliot's one doesn't:
15875 run, 15472 passes, 2 skipped, 88 expected failures, 216 failures, 99 errors, 0 unexpected passes
On the other hand, not being able to add a monticello directory repository is also not helpful. No filedialog is shown (receiver of bitAt: is nil, looks like a problem with filesystem permissions) Stephan
Eliot as a new VM as of yesterday http://www.mirandabanda.org/files/Cog/VM/VM.r2701/README.2701 That kind of fixes things. But I guess the Pharo team still has to integrate these fixes. BTW, here is the version string from the Cog VM explaining the "too old message": Smalltalk vm version. 'CoInterpreter VMMaker.oscog-eem.272 uuid: 8f4167f2-5bf0-4d90-9b7f-5355c741c68f Mar 11 2013 StackToRegisterMappingCogit VMMaker.oscog-eem.270 uuid: 014f0153-bb02-49b7-b544-d8f3ac2deef6 Mar 11 2013 VM: r2701 http://www.squeakvm.org/svn/squeak/branches/Cog Plugins: r2545 http://squeakvm.org/svn/squeak/trunk/platforms/Cross/plugins ' Obviously different :-) Phil 2013/3/12 Stephan Eggermont <stephan@stack.nl>:
Esteban wrote:
Eliot builds will always have the old vm warning, even if they are not old :)... you need one of the pharo builds (CogVM, NBCogVM or PharoVM)
Well, Doru reported they crashed. Eliot's one doesn't:
15875 run, 15472 passes, 2 skipped, 88 expected failures, 216 failures, 99 errors, 0 unexpected passes
On the other hand, not being able to add a monticello directory repository is also not helpful. No filedialog is shown (receiver of bitAt: is nil, looks like a problem with filesystem permissions)
Stephan
participants (2)
-
phil＠highoctane.be -
Stephan Eggermont