My observations for issue 12506
- I can reproduce it on linux
- segfault happens in primtiveNextInstance
- tests A-L worked in 30663
- tests A-L segfault since 30664
- doesn't segfaults anymore if you open the image, change some code, save and close the image
- it segfaults if you just run a subset of the A-L tests
(pharo --nodisplay Pharo.image test --junit-xml-output 'FileSystem-Tests-Core' 'FreeTypeTests' 'FileSystem-Tests-Disk' 'FuelTests' 'FileSystem-Tests-Memory' 'KernelTests')
- this "fail"-subset is different for the different images (30664, 30665, ...)
- it does not segfault if you omit the junit-xml-output option
-> Opal Regression Tests do run all tests (after recompiling) �> no problem ever
-> Monkey runs all tests for all �Fix review needed� �> no problem
And someone knows what happened with the image between version
30663 and 30666, because only
30664 and 30665 need the PharoV20.sources in the same directory as the VM,
for all other versions it suffices if the sources are where the image file is.
(Same as in
http://forum.world.st/pharo-3-0-image-td4732890.html)
30663:
12510 NautilusHistory entry for class methods loads instance methods
12502 FileList MNU FileSystemPermission>><=
12429 MessageBrowser loses changes
12451 Error on Browse Full in Nautilus from class in group view
30664
12517 SystemNavigation methodHierarchyBrowserForClass:selector: discards package information
12476 Undeclared
(remove Athens Tutorial as it introduces an Undeclared and was not in the image before)
(in addition, I downloaded the image, recompiled and uploaded a new seed image as latest.zip).
30665
- do not call #cleanUpForRelease on update
(to check if this was the reason for the crash, it was not)