Moose-dev March 2013

moose-dev@list.inf.unibe.ch

28 participants
207 discussions

Build failed in Jenkins: moose-latest-dev #1293

by admin＠moosetechnology.org

See <http://ci.moosetechnology.org:8020/job/moose-latest-dev/1293/> ------------------------------------------ Started by timer Building in workspace <http://ci.moosetechnology.org:8020/job/moose-latest-dev/ws/> [workspace] $ /bin/sh -xe /tmp/hudson4533343565087546929.sh + rm -rf <http://ci.moosetechnology.org:8020/job/moose-latest-dev/ws/moose> <http://ci.moosetechnology.org:8020/job/moose-latest-dev/ws/moose-tests> + /srv/ci.moosetechnology.org/builder/build.sh -i Pharo-1.4 -s monticello-fix-for-14 -s moose -s glamorous-theme -s moose-clean -s glamorous-toolkit -s cleanupforrelease -o moose [31m[33m =============================================================================== Notice: Errors in script loaded from <http://ci.moosetechnology.org:8020/job/moose-latest-dev/1293/artifact/moose…> =============================================================================== [0m[0m[31m==== Startup Error: Error: Name not found: FuelTestsCompatibilityBeforePharo20 [0mMetacelloMCVersionSpec(Object)>>error: MetacelloMCVersionSpec>>resolveToLoadableSpec:forMap:packages: in Block: [^ self error: 'Name not found: ' , aString] MetacelloMCVersionSpec>>packageNamed:forMap:ifAbsent: MetacelloMCVersionSpec>>resolveToLoadableSpec:forMap:packages: MetacelloMCVersionSpec>>resolveToLoadableSpecs:map: in Block: [:req | (self... Set>>do: MetacelloMCVersionSpec>>resolveToLoadableSpecs:map: MetacelloMCVersionSpec>>resolveToLoadableSpecs: MetacelloMCVersionSpec>>expandToLoadableSpecNames: in Block: [:cache | ... MetacelloPharoPlatform(MetacelloPlatform)>>stackCacheFor:cacheClass:at:doing: in Block: [:dict | ... [0m[31mGot startup errors: [0m[31m Error: Name not found: FuelTestsCompatibilityBeforePharo20 [0m blockNoContextSwitchOffset != null 9102 + /srv/ci.moosetechnology.org/builder/build.sh -i moose -s patch-inputsensor -s testrunner -s moose-tests -o moose-tests [31m[33m =============================================================================== Notice: Errors in script loaded from <http://ci.moosetechnology.org:8020/job/moose-latest-dev/ws/moose-tests/moos…> =============================================================================== [0m[0m[31m==== Startup Error: MessageNotUnderstood: receiver of "new" is nil [0mUndefinedObject(Object)>>doesNotUnderstand: #new UndefinedObject>>DoIt Compiler>>evaluate:in:to:notifying:ifFail:logged: Compiler class>>evaluate:for:notifying:logged: Compiler class>>evaluate:for:logged: Compiler class>>evaluate:logged: FileSystemFileStream(PositionableStream)>>fileInAnnouncing: in Block: [| chunk | val := (self peekFor: $!)... BlockClosure>>on:do: FileSystemFileStream(PositionableStream)>>fileInAnnouncing: in Block: [:bar | ... NonInteractiveUIManager(CommandLineUIManager)>>progressInitiationExceptionDefaultAction: [0m[31mGot startup errors: [0m[31m MessageNotUnderstood: receiver of "new" is nil [0m blockNoContextSwitchOffset != null 9102 + /srv/ci.moosetechnology.org/builder/build-oneclick.sh -i moose -o moose_suite-4_7_dev -n Moose -t 'Moose Suite 4.7 Development ' -v 4.7 -c Moose cp: cannot stat `/srv/ci.moosetechnology.org/builder/oneclick-icons/Moose.png': No such file or directory cp: cannot stat `/srv/ci.moosetechnology.org/builder/oneclick-icons/Moose.ico': No such file or directory cp: cannot stat `/srv/ci.moosetechnology.org/builder/oneclick-icons/Moose.icns': No such file or directory /srv/ci.moosetechnology.org/builder/build-oneclick.sh: line 170: zip: command not found Recording test results No test report files were found. Configuration error? Build step 'Publish JUnit test result report' changed build result to FAILURE Archiving artifacts

11 years, 9 months

strongSelectin in Glamour

by Nicolas Anquetil

Hi, I have a browser with some kind of "buffer" where I can hold a value selected from one of several list in the browser. The buffer itself is implemented as a pane containing a list with only one element in it, it is populated when I strongSelect (double click) in one of the source list: (browser transmit) to: #buffer; from: #PackagePane port: #strongSelection; andShow: [:a | a list display: [:anEntity | {anEntity} ] ]. (browser transmit) to: #buffer; from: #ClassPane port: #strongSelection; andShow: [:a | a list display: [:anEntity | {anEntity} ] ]. I also transmit from one list to the other with simple selection (click) (browser transmit) to: #ClassPane; from: #PackagePane; andShow: [:b | | gmlList | gmlList := b list. gmlList display: [:anEntity | anEntity classes]]; It works "thusly" : if I click on a package in the PackagePane, its class appear in the ClassPane. If I double click on a package or a class, then it also appears in the "buffer" However, if I double click on a class, it goes correctly in the buffer, but if after I single click on a package, the "buffer" is wiped. This is not the intended behavior ... Bug or feature? and if it is a feature, how to get the feature I want? nicolas -- Nicolas Anquetil -- RMod research team (Inria)

11 years, 9 months

missing pharo sources warning in Moose 4.8

by Usman Bhatti

There is a warning in Moose 4.8 regarding the absence of pharo sources. I had added these sources in the build (the artifacts produced by the build). Did someone modify the job to remove the sources from the latest Moose build? usman [image: Inline image 2]

11 years, 9 months

Moose logo and glamour-theme?

by Usman Bhatti

Moose 4.8 image does not have a moose logo and glamour-related theme. Do we want to continue the settings from 1.4 (a custom moose logo and glamour-theme) or should we just use the logo and the look/theme that comes with Pharo? usman

11 years, 9 months

Issue 919 in moose-technology: Moose Panel does not open in on Moose-latest-dev-4.8 image

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 919 by hayatouo...(a)gmail.com: Moose Panel does not open in on Moose-latest-dev-4.8 image http://code.google.com/p/moose-technology/issues/detail?id=919 When I try World--->Moose--->Moose Panel. I get this message : MessageNotUnderstood: MoosePanel>>#openOn: Attachments: screenshot.png 36.9 KB -- 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

11 years, 9 months

jenkins is triggered by a commit in moose

by Tudor Girba

Hi, I configured Jenkins to trigger at every commit in the Moose repository. However, it will not trigger when committing to something like Glamour. What we should do now is to create jobs for each of the sub-projects and have those listen to their respective repositories. Afterwards, we make the moose-latest-dev build to be triggered by these sub-jobs. Like that we ensure two things: - every sub-project can be loaded independently - every commit will be checked as soon as possible Of course, ideally, we should also have the builds ran faster, but that is another story :) Cheers, Doru -- www.tudorgirba.com "Quality cannot be an afterthought."

11 years, 9 months

glamour question

by Fabrizio Perin

Hi, I was writing a report in Arki. The result of the report is a dictionary. An entry of the dictionary has as key a FAMIXMethod and as value an ordered collection with inside one or more ordered collections. What I want to do is to have a browser with two rows, in the top row I want a MooseFinder opening on the keys of the dictionary, on the bottom row I want to see the content of the dictionary at the selected key. The problem is that I'm not able to make the MooseFinder opening on the keys of the element. Here a script that reproduce this scenario: | dic myBrowser | dic := Dictionary new. dic at: FAMIXMethod new put: (OrderedCollection with: (OrderedCollection with: 1 with: 2 with: 3)). dic at: FAMIXMethod new put: (OrderedCollection with: (OrderedCollection with: 4 with: 5 with: 6)). dic at: FAMIXMethod new put: (OrderedCollection with: (OrderedCollection with: 7 with: 8 with: 9)). myBrowser := GLMTabulator new. myBrowser row: #methods; row: #info. myBrowser transmit to: #methods; andShow: [:a | a custom: (MooseFinder new first startOn: dic keys asMooseGroup) ]. myBrowser transmit to: #info; from: #methods; andShow: [:a | a list title: 'Columns to map'; display: [:method | (self result at: method) ]]. myBrowser openOn: dic. Any suggestion will be more than welcome. Thanks. Cheers, Fabrizio

11 years, 9 months

Falling test question

by Andre Hora

Hi, Test MooseSmalltalkImporterRoelTyperTest>>testASTCore is falling because at some point it is using class TypeCollector, which is no longer in the system. So what should we do: - Remove this importer? - Bring back TypeCollector? ======== SmalltalkImporter>>createAttribute: name for: aClass ... ifTrue: [ possibleTypes := (TypeCollector typeInstvar: name asSymbol ofClassWithLookup: aClass ) types. possibleTypes size = 1 ifTrue: [attribute declaredType: (self ensureClass: possibleTypes first theNonMetaClass) ]. ]. ^ attribute ========= -- Andre Hora

11 years, 9 months

working moose build

by Tudor Girba

Hi, The Moose build including running tests now works based on the NBCog VM and the latest Pharo 2.0 (built on Ubuntu): https://ci.inria.fr/moose/job/Moose-latest-dev-4.8/lastCompletedBuild/testR… There are 27 test failures. I also tried on OS X using NBCog VM and the there is no crash. This scenario was also confirmed by Stephan although he reported more failures. For reference, we are using the following script on Jenkins: wget --quiet -qO - http://pharo.gforge.inria.fr/ci/script/ciPharo20NBCogVM.sh | bash wget http://pharo.gforge.inria.fr/ci/image/PharoV20.sources ./vm.sh Pharo.image save $JOB_NAME REPO=http://smalltalkhub.com/mc/Moose/Moose/main ./vm.sh $JOB_NAME.image config $REPO ConfigurationOfMoose --install=development ./vm.sh $JOB_NAME.image moosetest --junit-xml-output zip -r $JOB_NAME.zip $JOB_NAME.image $JOB_NAME.changes PharoV20.sources Cheers, Doru -- www.tudorgirba.com "From an abstract enough point of view, any two things are similar."

11 years, 9 months

Re: [Pharo-project] where to report vm crashes? (while running Moose tests)

by Tudor Girba

It would be good to have a parallel job, but the problem is that you will get a message saying that the VM is too old for the Pharo 2.0 image. Cheers, Doru On Tue, Mar 12, 2013 at 9:05 AM, Usman Bhatti <usman.bhatti(a)gmail.com>wrote: > Doru, > > In the meantime, can we revert to CogVM because currently we cannot see > the status of fixes and we cannot go any further with Moose 4.8 or may be > create parallel jobs on Cog and Pharo vms ? > > > > On Mon, Mar 11, 2013 at 9:53 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Hi, >> >> Where should I report Pharo VM crashes with Pharo 2.0? >> >> In particular, I wanted to report the problem related to running Moose >> tests from the command line: >> >> --- >> You can reproduce it on Mac, quite consistently: just run the attached >> script (you need to have wget installed), or do it manually: >> >> 1. download and unzip the latest Moose 4.8: >> >> https://ci.inria.fr/moose/job/Moose-latest-dev-4.8/lastSuccessfulBuild/arti… >> 2. download and unzip the latest Pharo VM: >> http://pharo.gforge.inria.fr/ci/vm/pharo/mac/pharo-mac-latest.zip >> 3. execute: >> ./Pharo.app/Contents/MacOS/Pharo ./Moose-latest-dev-4.8.image moosetest >> >> The VM crashes, but there is no trace of the error. >> --- >> >> >> Cheers, >> Doru >> >> >> -- >> www.tudorgirba.com >> >> "It's not what we do that matters most, it's how we do it." >> >> > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- www.tudorgirba.com "Every thing has its own flow"

11 years, 9 months

← Newer
1
...
11
12
13
14
15
16
17
...
21
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev March 2013