Moose-dev August 2013

moose-dev@list.inf.unibe.ch

26 participants
167 discussions

Build failed in Jenkins: moose-latest-dev-4.8 #853
by admin＠moosetechnology.org 11 Aug '13

11 Aug '13

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/853/> ------------------------------------------ Started by user tudor(a)tudorgirba.com Building remotely on moose-ubuntu1204-dualproc-i386 in workspace <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/> Deleting project workspace... done [moose-latest-dev-4.8] $ /bin/sh -xe /tmp/hudson4028892227397677743.sh + + bash wget --quiet -O - http://get.pharo.org/20+vmLatest Downloading the latest 20 Image: http://files.pharo.org/image/20/latest.zip Pharo.image Downloading the latest pharoVM: http://files.pharo.org/vm/pharo/linux/latest.zip pharo-vm/pharo Downloading PharoV10.sources: http://files.pharo.org/sources//PharoV10.sources.zip Downloading PharoV20.sources: http://files.pharo.org/sources//PharoV20.sources.zip Creating starter scripts pharo and pharo-ui + ./pharo Pharo.image save moose-latest-dev-4.8 + REPO=http://www.smalltalkhub.com/mc/Moose/Moose/main + ./pharo moose-latest-dev-4.8.image config http://www.smalltalkhub.com/mc/Moose/Moose/main ConfigurationOfMoose --install=development [31m[33m =============================================================================== Notice: Installing ConfigurationOfMoose development =============================================================================== [0m[0m+ ./pharo moose-latest-dev-4.8.image mooseimagesetup --signature=https://ci.inria.fr/moose/job/moose-latest-dev-4.8/853/ [31m==== Startup Error: MessageNotUnderstood: MooseImage>>description: [0mMooseImage(Object)>>doesNotUnderstand: #description: MooseImageSetupCommandLineHandler>>installImageDescription MooseImageSetupCommandLineHandler>>activate MooseImageSetupCommandLineHandler class(CommandLineHandler class)>>activateWith: DefaultCommandLineHandler>>handleSubcommand DefaultCommandLineHandler>>handleArgument: DefaultCommandLineHandler>>activate DefaultCommandLineHandler class>>startUp: in Block: [self new activate] BlockClosure>>cull: SmalltalkImage>>executeDeferredStartupActions: in Block: [each cull: resuming] BlockClosure>>on:do: SmalltalkImage>>logStartUpErrorDuring:into:tryDebugger: SmalltalkImage>>executeDeferredStartupActions: in Block: [:each | self... OrderedCollection>>do: SmalltalkImage>>executeDeferredStartupActions: SmalltalkImage>>startupImage:snapshotWorked: SmalltalkImage>>snapshot:andQuit: ConfigurationCommandLineHandler>>installVersion: ConfigurationCommandLineHandler>>installConfiguration ConfigurationCommandLineHandler>>activate ConfigurationCommandLineHandler class(CommandLineHandler class)>>activateWith: DefaultCommandLineHandler>>handleSubcommand DefaultCommandLineHandler>>handleArgument: DefaultCommandLineHandler>>activate DefaultCommandLineHandler class>>startUp: in Block: [self new activate] BlockClosure>>cull: SmalltalkImage>>executeDeferredStartupActions: in Block: [each cull: resuming] BlockClosure>>on:do: SmalltalkImage>>logStartUpErrorDuring:into:tryDebugger: SmalltalkImage>>executeDeferredStartupActions: in Block: [:each | self... [0m[31mGot startup errors: [0m[31m MessageNotUnderstood: MooseImage>>description: [0mBuild step 'Execute shell' marked build as failure Archiving artifacts Recording test results

1 0

Build failed in Jenkins: moose-latest-dev-4.8 #851
by admin＠moosetechnology.org 11 Aug '13

11 Aug '13

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/851/> ------------------------------------------ Started by user tudor(a)tudorgirba.com Building remotely on moose-ubuntu1204-dualproc-i386 in workspace <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/> Deleting project workspace... done [moose-latest-dev-4.8] $ /bin/sh -xe /tmp/hudson9046971053432843357.sh + wget --quiet -O - http://get.pharo.org/20+vmLatest + bash Downloading the latest 20 Image: http://files.pharo.org/image/20/latest.zip Pharo.image Downloading the latest pharoVM: http://files.pharo.org/vm/pharo/linux/latest.zip pharo-vm/pharo Downloading PharoV10.sources: http://files.pharo.org/sources//PharoV10.sources.zip Downloading PharoV20.sources: http://files.pharo.org/sources//PharoV20.sources.zip Creating starter scripts pharo and pharo-ui + ./pharo Pharo.image save moose-latest-dev-4.8 + REPO=http://www.smalltalkhub.com/mc/Moose/Moose/main + ./pharo moose-latest-dev-4.8.image config http://www.smalltalkhub.com/mc/Moose/Moose/main ConfigurationOfMoose --install=development [31m[33m =============================================================================== Notice: Installing ConfigurationOfMoose development =============================================================================== [0m[0m+ ./pharo moose-latest-dev-4.8.image mooseimagesetup --signature=https://ci.inria.fr/moose/job/moose-latest-dev-4.8/851/ [31m==== Startup Error: MessageNotUnderstood: MooseImage>>timestamp: [0mMooseImage(Object)>>doesNotUnderstand: #timestamp: MooseImageSetupCommandLineHandler>>installImageDescription MooseImageSetupCommandLineHandler>>activate MooseImageSetupCommandLineHandler class(CommandLineHandler class)>>activateWith: DefaultCommandLineHandler>>handleSubcommand DefaultCommandLineHandler>>handleArgument: DefaultCommandLineHandler>>activate DefaultCommandLineHandler class>>startUp: in Block: [self new activate] BlockClosure>>cull: SmalltalkImage>>executeDeferredStartupActions: in Block: [each cull: resuming] BlockClosure>>on:do: SmalltalkImage>>logStartUpErrorDuring:into:tryDebugger: SmalltalkImage>>executeDeferredStartupActions: in Block: [:each | self... OrderedCollection>>do: SmalltalkImage>>executeDeferredStartupActions: SmalltalkImage>>startupImage:snapshotWorked: SmalltalkImage>>snapshot:andQuit: ConfigurationCommandLineHandler>>installVersion: ConfigurationCommandLineHandler>>installConfiguration ConfigurationCommandLineHandler>>activate ConfigurationCommandLineHandler class(CommandLineHandler class)>>activateWith: DefaultCommandLineHandler>>handleSubcommand DefaultCommandLineHandler>>handleArgument: DefaultCommandLineHandler>>activate DefaultCommandLineHandler class>>startUp: in Block: [self new activate] BlockClosure>>cull: SmalltalkImage>>executeDeferredStartupActions: in Block: [each cull: resuming] BlockClosure>>on:do: SmalltalkImage>>logStartUpErrorDuring:into:tryDebugger: SmalltalkImage>>executeDeferredStartupActions: in Block: [:each | self... [0m[31mGot startup errors: [0m[31m MessageNotUnderstood: MooseImage>>timestamp: [0mBuild step 'Execute shell' marked build as failure Archiving artifacts Recording test results

1 0

Another problem GlamourExamples and EyeSee and others
by Stéphane Ducasse 11 Aug '13

11 Aug '13

HI doru GLMBrowserTemplate You must resolve these dependencies before you will be able to load these definitions: GLMEyeSeeExamplesBrowser I checked and GLMEyeSeeExamplesBrowser class >> open ^ self new openOn: ESExamples package: 'Glamour-Examples' ; look bogus it depends on Magritte!, EyeSee and Roassal I tried package: 'Glamour-Examples' with: [spec requires: #('Glamour-Magritte-Presentations' 'Glamour-EyeSee-Presentations' 'Glamour-Mondrian-Presentations')] ; but I navigate in the total guess here. Can you have a look? Stef

2 2

Problem: Mondrian-ComplexShape depends on MONodeShape
by Stéphane Ducasse 11 Aug '13

11 Aug '13

So I did package: 'Mondrian-Core'; package: 'Mondrian-ComplexShape' with: [ spec requires: 'Mondrian-Core' ]; package: 'Mondrian-Layouts'; and restarted again….

1 3

Another problem (Mondrian-Pharo-Tests)
by Stéphane Ducasse 11 Aug '13

11 Aug '13

Mondrian-Pharo-Tests says This package depends on the following classes: MondrianTest You must resolve these dependencies before you will be able to load these definitions: MOCanvasTest allEventPollsEmpty I'm trying to find the problem now but in parallel I'm painting my house door :) Stef

1 2

SnapshotCello feedabck
by Stéphane Ducasse 11 Aug '13

11 Aug '13

Hi doru I like the interface much better than the moose reloader :) Else - what about dirty packages that are not in the configuration tree? I would not handle them to force people to get clean Did you try to rebuild Moose using it? I will ;) Stef

2 23

Issue 960 in moose-technology: Smalltalk importer creates a non-stub Object.DependentsFields
by moose-technology＠googlecode.com 10 Aug '13

10 Aug '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-SmalltalkImporter New issue 960 by anquetil...(a)gmail.com: Smalltalk importer creates a non-stub Object.DependentsFields http://code.google.com/p/moose-technology/issues/detail?id=960 When creating a moose model from smalltalk code not including Object The class Object is created with isStub=true Object has an attribute Object.DependentsFields (a class variable) with isStub=false -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

1 3

Issue 962 in moose-technology: Metanool should not extend MooseEntity and MooseGroup
by moose-technology＠googlecode.com 10 Aug '13

10 Aug '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Milestone-4.8 Component-Metanool Component-Finder New issue 962 by tu...(a)tudorgirba.com: Metanool should not extend MooseEntity and MooseGroup http://code.google.com/p/moose-technology/issues/detail?id=962 Metanool extends these classes with MooseFinder specific methods. These methods should move to MooseFinder. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

1 1

ConfigurationOfMondrian is reallllllllllly old!!!!
by Stéphane Ducasse 10 Aug '13

10 Aug '13

Hi guys Is Moose really using development version of its subproject? because spec project: 'Mondrian' with: [ spec className: 'ConfigurationOfMondrian'; file: 'ConfigurationOfMondrian'; version: #development ; repository: 'http://www.smalltalkhub.com/mc/Moose/Mondrian/main' And development: spec <symbolicVersion: #'development'> spec for: #'common' version: '2.162'. and there are <version: '2.9' imports: #('2.5-baseline')> So when I do (ConfigurationOfMoose project version: #development) record loadDirective for moose I get … (ConfigurationOfMoose project version: #development) record loadDirective I get No version found for 1.3 of ConfigurationOfShout!!!

2 5

Conceptual Limit of SnapshotCello ?
by Stéphane Ducasse 10 Aug '13

10 Aug '13

Hi doru I'm trying to reload a configuration for moose and I end up with package loading order problems. I thought that in reloader we payed attention to preserve the same loading order (I remember that we did it when I was attending the moose workshop). Now do you know if the baseline of a project is not interfering with the load order that we store. Stef

2 3

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev August 2013