I downloaded Windows (32 bit only). Played around and had no visible issues so I ran the tests and got some errors and failures (I don't know whether they're expected):
14425 run, 14342 passes, 29 skipped, 57 expected failures, 17 failures, 9 errors, 0 unexpected passes Failures: MCSnapshotBrowserTest>>#testNoSelection MCWorkingCopyTest>>#testSimpleMerge MCStWriterTest>>#testInitializerDefinition MetacelloRepositorySqueakCommonTestCase>>#testDirectoryRepository MetacelloRepositorySqueakCommonTestCase>>#testAsRepositorySpecFor MCSnapshotTest>>#testCreation MCWorkingCopyTest>>#testOptimizedLoad MCSnapshotBrowserTest>>#testClassSelected ReleaseTest>>#testMethodsWithUnboundGlobals MCSnapshotBrowserTest>>#testCategorySelected MCWorkingCopyTest>>#testRepeatedMerge MCSnapshotBrowserTest>>#testClassSideClassSelected MCPatchTest>>#testPatchContents ZnClientTests>>#testIfFailNotFound MCWorkingCopyTest>>#testSelectiveBackport MCWorkingCopyTest>>#testSnapshotAndLoad GLMRubricTextMorphicTest>>#testPastingUpdatesTextPort Errors: MCPackageTest>>#testUnloadWithAdditionalTracking MCSnapshotBrowserTest>>#testMethodIsCleared MCSnapshotBrowserTest>>#testMethodSelected MCSnapshotBrowserTest>>#testProtocolIsCleared MCSnapshotBrowserTest>>#testProtocolSelected MCStWriterTest>>#testClassMethodDefinition MCStWriterTest>>#testMethodDefinition MCWorkingCopyTest>>#testBackport MCFileInTest>>#testStWriter Best regards! Esteban A. Maringolo 2017-05-31 13:39 GMT-03:00 Esteban Lorenzano <[email protected]>: > But I tested Roassal (and Athens) in 64bits and they were working. > What changed? > > On 31 May 2017, at 18:33, Alexandre Bergel <[email protected]> wrote: > > Hi Volkert, > > Roassal does not work on Pharo 64-bits. The issue here is Athens. > > When Pharo 6 will be released, we will evaluate the options to make Roassal > run on 64 bits. The option I see, is using Pompeii, the backend by Ronie > that uses directly OpenGL. This works well on Pharo 64 bits. > > Someone see another option? > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On May 31, 2017, at 12:24 PM, volkert <[email protected]> wrote: > > Downloaded Linux 64 Bit. > Installed Roassal. > Run Examples. > VM crashed :-( > > BW, Volkert > > Am 31.05.2017 um 17:59 schrieb Esteban Lorenzano: > > On 31 May 2017, at 17:46, Peter Uhnak <[email protected]> wrote: > > I find the Windows distribution a bit chaotic as all the files (vm, vm libs, > image, sources) are in the same folder. Maybe there were issues with using > shortcuts? Because then launching the image will also create pharo-local in > the folder (and any other file that image writes to imageDirectory), so it > could be more chaos for a new user. > > yes, it has been like that since some time and we need to change it… but not > now for release :) > > The linux distro contains sources twice > 1) pharo6.0/shared/PharoV60.sources > 2) pharo6.0/bin/PharoV60.sources > > yeah, that’s also a problem from one-click days… maybe I can fix that/ > > Esteban > > Peter > > > On Wed, May 31, 2017 at 04:18:19PM +0200, Esteban Lorenzano wrote: > > Hello, > > we are getting ready for release. > please take a minute to review: > > http://pharo.org/STAGE.download <http://pharo.org/STAGE.download> > > (notice that zerconf download will not work because it is not yet moved… so > #stable will download current stable version which is 5.0) > > cheers, > Esteban > > >
