- Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #1012: 5232-Remove-GTEventRecorder-
by ci-pharo-ci-jenkins2＠inria.fr Nov. 26, 2019

Nov. 26, 2019

There is a new Pharo build available! The status of the build #1012 was: FAILURE. The Pull Request #5236 was integrated: "5232-Remove-GTEventRecorder-" Pull request url: https://github.com/pharo-project/pharo/pull/5236 Issue Url: https://github.com/pharo-project/pharo/issues/5232 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1011: 5233-Integrate-EnlumineurFormatter
by ci-pharo-ci-jenkins2＠inria.fr Nov. 26, 2019

Nov. 26, 2019

There is a new Pharo build available! The status of the build #1011 was: FAILURE. The Pull Request #5234 was integrated: "5233-Integrate-EnlumineurFormatter" Pull request url: https://github.com/pharo-project/pharo/pull/5234 Issue Url: https://github.com/pharo-project/pharo/issues/5233 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

VM crash investigations
by Alistair Grant Nov. 26, 2019

Nov. 26, 2019

Hi All, At the moment I'm spending pretty much all of my working time tracking down VM crashes. It sounds like there may be others working on the same issue (Guille?, Pablo?), if so it would be good to be able to exchange notes and hopefully reach a resolution a little earlier. So my status... I'm currently focusing on two corruptions that I've seen: 1. Frame Pointers aren't being updated when the receiver or rcvr/clsr they point to is moved during scavenging / compaction. 2. The current frame pointer (framePointer) contains an address that is in a free stack page. I'm doing all the investigation using a Pharo minimal image, so there's no FreeType, and from what I've seen FFI isn't being used. The script I'm using to reproduce the crash is at: https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/444#issuecomment-5… (the good part about this is that even the memory addresses are consistent across runs, so it is highly reproducible). For the Frame Pointers not being updated, what I'm seeing is that after a scavenge has finished copying all the referenced objects, but before the survivor spaces are exchanged, the call stack looks like: (gdb) call printCallStack() 0x7ffffffe3f70 I SessionManager>launchSnapshot:andQuit: 0x1508860: a(n) SessionManager 0x7ffffffe3fe0 I [] in SessionManager>snapshot:andQuit: 0x1508860: a(n) SessionManager 0x7ffffffe4020 I [] in INVALID RECEIVER>newProcess 0x118a728 0x118a728 is a forwarded object to 0x488fca0 of slot size 7 hdr8 ..... Once the survivor spaces have been exchanged: (gdb) call printCallStack() 0x7ffffffe3f70 I SessionManager>launchSnapshot:andQuit: 0x1508860: a(n) SessionManager 0x7ffffffe3fe0 I [] in SessionManager>snapshot:andQuit: 0x1508860: a(n) SessionManager 0x7ffffffe4020 I [] in INVALID RECEIVER>newProcess 0x118a728 is in new space For the framePointer containing an address in a free stack page: adding a check during the scavenge shows that the framePointer is in a free page. I'm assuming it is never valid for the framePointer to be in a free stack page, and that the receiver and rcvr/clsr should never be in new space. If my assumptions are wrong please let me know. If you'd like any more information, please let me know. Thanks, Alistair

3 3

[Pharo 8.0] Build #1010: 5212-Executable-comment-checker-problem
by ci-pharo-ci-jenkins2＠inria.fr Nov. 26, 2019

Nov. 26, 2019

There is a new Pharo build available! The status of the build #1010 was: FAILURE. The Pull Request #5224 was integrated: "5212-Executable-comment-checker-problem" Pull request url: https://github.com/pharo-project/pharo/pull/5224 Issue Url: https://github.com/pharo-project/pharo/issues/5212 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1009: 5217-Remove-blueInk-to-introduce-Enlumineur
by ci-pharo-ci-jenkins2＠inria.fr Nov. 25, 2019

Nov. 25, 2019

There is a new Pharo build available! The status of the build #1009 was: FAILURE. The Pull Request #5218 was integrated: "5217-Remove-blueInk-to-introduce-Enlumineur" Pull request url: https://github.com/pharo-project/pharo/pull/5218 Issue Url: https://github.com/pharo-project/pharo/issues/5217 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1008: Completion: Fix emebdded Browser
by ci-pharo-ci-jenkins2＠inria.fr Nov. 25, 2019

Nov. 25, 2019

There is a new Pharo build available! The status of the build #1008 was: FAILURE. The Pull Request #5220 was integrated: "Completion: Fix emebdded Browser" Pull request url: https://github.com/pharo-project/pharo/pull/5220 Issue Url: https://github.com/pharo-project/pharo/issues/CompletionFixBrowser Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

DrTest - strange UI effect and some feedback
by Torsten Bergmann Nov. 25, 2019

Nov. 25, 2019

Hi, DrTest is integrated into Pharo 8 now - but there seems to be a strange bug in overlapping widgets when one uses the grouping selection box. See attached screenshot. I opened an issue for that: https://github.com/pharo-project/pharo/issues/5205 for Pharo. Dont know if that is known bug or even already fixed in the original repo of DrTest. Would be good if the authors (Julien or Dayne) could check. Additional feedback: It's really a nice tool - but I see myself still switching back to old TestRunner again. Two reasons: 1. Compared to the regular TestRunner where one is able to see the failing tests directly in DrTest one always has to have additional clicks in the grouping tree on the left before getting the final results. So the default grouping of the results as a tree could be disturbing because it requires more clicking around. Would be a nice addition if there would be an additional "no grouping" mode as well so the results are just shown in a list like in reglar TestRunner. 2. The old TestRunner had (after filtering the package) an additional useful context menu with "Select all" and "Select none", "Select inversion", .... which allowed easier focusing on the test classes I want to check. Would be nice if a similar one could be added. Thanks T.

4 4

[ANN] Next Pharo Sprint: Nov 29
by Marcus Denker Nov. 25, 2019

Nov. 25, 2019

We will organize a Pharo sprint / Moose dojo Nov 29, starting at 10:00am. (Local Time Paris). Goals of this sprint: - Pharo 8: Fix issues from tracker https://github.com/pharo-project/pharo/issues <https://github.com/pharo-project/pharo/issues> Remote Sprint: Remotely, you can join us on Discord. During the sprint, we synchronize local and remote Pharo sprinters: http://pharo.org/contribute-events <http://pharo.org/contribute-events> We have added a Board to coordinate the work: https://github.com/orgs/pharo-project/projects/9 <https://github.com/orgs/pharo-project/projects/9> Known Local Sprint meetings - Lille/France: It will be at the Inria Lille, Building B, third floor (RMoD offices). As the building is not open to the public, please contact us before if you plan to come A list of all Pharo Event of the year an be found here: https://association.pharo.org/events <https://association.pharo.org/events>

1 0

[Pharo 8.0] Build #1007: 5213-Little-pass-on-DrTests
by ci-pharo-ci-jenkins2＠inria.fr Nov. 24, 2019

Nov. 24, 2019

There is a new Pharo build available! The status of the build #1007 was: FAILURE. The Pull Request #5214 was integrated: "5213-Little-pass-on-DrTests" Pull request url: https://github.com/pharo-project/pharo/pull/5214 Issue Url: https://github.com/pharo-project/pharo/issues/5213 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1006: Reflectivity: ASTCacheReset not needed
by ci-pharo-ci-jenkins2＠inria.fr Nov. 23, 2019

Nov. 23, 2019

There is a new Pharo build available! The status of the build #1006 was: FAILURE. The Pull Request #5210 was integrated: "Reflectivity: ASTCacheReset not needed" Pull request url: https://github.com/pharo-project/pharo/pull/5210 Issue Url: https://github.com/pharo-project/pharo/issues/ReflectivityNoASTCacheReset Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0