- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 4003 in pharo: Build of Core 1.3 broken because of integration of 13147

by pharo＠googlecode.com

Updates: Status: FixToInclude Comment #5 on issue 4003 by marcus.d...(a)gmail.com: Build of Core 1.3 broken because of integration of 13147 http://code.google.com/p/pharo/issues/detail?id=4003 I think the problem is a exception handler that swallows all Exceptions (ProgressNotification, too) in headless mode. (leftover from before the real headless mode). fix attached. Attachments: SmalltalkImage-sendtoClassesNamedInwith.st 886 bytes

April 13, 2011

Re: [Pharo-project] Issue 4003 in pharo: Build of Core 1.3 broken because of integration of 13147

by pharo＠googlecode.com

Comment #4 on issue 4003 by marcus.d...(a)gmail.com: Build of Core 1.3 broken because of integration of 13147 http://code.google.com/p/pharo/issues/detail?id=4003 Now the script loads but we get a walkback. One that does not kill the image interestingly. https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.3/ws/PharoCore-…

April 13, 2011

Re: [Pharo-project] Issue 4003 in pharo: Build of Core 1.3 broken because of integration of 13147

by pharo＠googlecode.com

Comment #3 on issue 4003 by marcus.d...(a)gmail.com: Build of Core 1.3 broken because of integration of 13147 http://code.google.com/p/pharo/issues/detail?id=4003 I think I found it. I added CommandLine initialize to the postscript but forgot CodeLoader initialize

April 13, 2011

Re: [Pharo-project] Issue 4003 in pharo: Build of Core 1.3 broken because of integration of 13147

by pharo＠googlecode.com

Comment #2 on issue 4003 by marcus.d...(a)gmail.com: Build of Core 1.3 broken because of integration of 13147 http://code.google.com/p/pharo/issues/detail?id=4003 So I did a new prebuild. https://gforge.inria.fr/frs/download.php/28478/PharoCore-1.3-13147.zip But now Hudson hangs when loading the script. So something is completely broken. https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.3/215/console

April 13, 2011

Re: [Pharo-project] Issue 4002 in pharo: AbstractLauncher needs to be removed

by pharo＠googlecode.com

Comment #1 on issue 4002 by ryd...(a)gmail.com: AbstractLauncher needs to be removed http://code.google.com/p/pharo/issues/detail?id=4002 Security? That script could contain sinister arbitrary code! :)

April 13, 2011

Re: [Pharo-project] Issue 4003 in pharo: Build of Core 1.3 broken because of integration of 13147

by pharo＠googlecode.com

Comment #1 on issue 4003 by marcus.d...(a)gmail.com: Build of Core 1.3 broken because of integration of 13147 http://code.google.com/p/pharo/issues/detail?id=4003 I think changing how scripts are loaded in an image started with a script is not good. The image itself when updated seems good. So I update the pre-build and we will see.

April 13, 2011

[Pharo-project] Issue 4004 in pharo: Obsolete class references to AutoStart

by pharo＠googlecode.com

Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3 New issue 4004 by marcus.d...(a)gmail.com: Obsolete class references to AutoStart http://code.google.com/p/pharo/issues/detail?id=4004 Two methods: #loadUpdateFromServerAtStartup AbstractLauncher class autoStarter ScriptLoader update13147

April 13, 2011

[Pharo-project] Issue 4003 in pharo: Build of Core 1.3 broken because of integration of 13147

by pharo＠googlecode.com

Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3 New issue 4003 by marcus.d...(a)gmail.com: Build of Core 1.3 broken because of integration of 13147 http://code.google.com/p/pharo/issues/detail?id=4003 Issue 13147 has some problem: + /builds/builder/build13.sh -i gforgeCore13 -s update -o PharoCore-1.3 Segmentation fault 2031166104 Behavior>allInstancesDo: 2031165968 Behavior>allSubInstancesDo: 2031165876 Behavior>allSubInstances 2031165724 >shutDown: 2031165632 SmalltalkImage>send:toClassesNamedIn:with: 2031165540 BlockClosure>on:do: 2031165448 SmalltalkImage>send:toClassesNamedIn:with: 2031148208 OrderedCollection>do: 2031148116 SmalltalkImage>send:toClassesNamedIn:with: 2031148024 SmalltalkImage>processShutDownList: 2031132380 SmalltalkImage>snapshot:andQuit: 2031132288 UndefinedObject>? 2028739856 WorldState>runStepMethodsIn: 2028739764 PasteUpMorph>runStepMethods 2025422416 WorldState>doOneCycleNowFor: 2025422324 WorldState>doOneCycleFor: 2025422232 PasteUpMorph>doOneCycle 2015335972 >? 2015335880 BlockClosure>? /tmp/hudson2223222193118569935.sh: line 3: 19842 Aborted /builds/builder/build13.sh -i gforgeCore13 -s update -o PharoCore-1.3 Archiving artifacts Enregistrement des r?sultats des tests

April 13, 2011

[Pharo-project] Issue 4002 in pharo: AbstractLauncher needs to be removed

by pharo＠googlecode.com

Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3 New issue 4002 by marcus.d...(a)gmail.com: AbstractLauncher needs to be removed http://code.google.com/p/pharo/issues/detail?id=4002 ...make sure to rewrite the SystemSettings references. I think we should remove #readDocumentAtStartup Why would one ever not lead a script that is given as a command line option?

April 13, 2011

[Pharo-project] [update 1.3] #13147

by Marcus Denker

13147 ----- Issue 3818: CommandLine Manager (some cleanup of Undeclared AutoStart will be needed later) -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

April 13, 2011