Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

improved ci
by Tudor Girba 23 Mar '13

23 Mar '13

Hi, Over the past week I worked on strengthening the new Jenkins infrastructure: - created multiple jobs for Moose subprojects like Fame, Glamour or PetitParser. We should continue to create such jobs for all projects. - Made the jobs to react on commits to the respective repositories, and to trigger the full Moose build. Like this we both ensure that every individual project is loadable as standalone, and we ensure that the integration tests are run after every commit. - created shortcuts: ci.moosetechnology.org -> https://ci.inria.fr/moose/ ci.moosetechnology.org//moose-latest-dev.zip -> https://ci.inria.fr/moose/job/moose-latest-dev-4.8/lastSuccessfulBuild/arti… Cheers, Doru -- www.tudorgirba.com "To utilize feedback, you first have to acquire it."

3 2

Glamour Roassal edgesFrom in nested layout (4.8)
by Stephan Eggermont 22 Mar '13

22 Mar '13

Hi, I am trying to get the edges to superclass to cross the package boundary. Could be related to Issue 845 Cheers, Stephan a roassal title: 'Complexity'; painting: [:view| | packages classes allClasses | packages := RPackageOrganizer default packages select: [ :p | p packageName beginsWith: 'Inno-' ]. allClasses := IdentitySet new. packages do: [ :package | allClasses addAll: package classes ]. view shape rectangle. view nodes: packages forEach: [ :aPackage | view interaction action: #browse. view shape rectangle width: [:cls | cls instVarNames size * 3]; height: [:cls | cls methods size ]; fillColor: (RONColorLinearNormalizer inContext: (allClasses) withCommand: [:cls | cls methods inject: 0 into: [:sum :el | sum + el getSource lineCount]] lowColor: Color green highColor: Color red). view nodes: aPackage classes. view edgesFrom: #superclass. view treeLayout ]. view gridLayout ]

2 1

Extra ^ test on petitparser compositeparsers?
by Stephan Eggermont 22 Mar '13

22 Mar '13

Hi, Would it make sense to test PPCompositeParser subclasses to not end with returnSelf for productions? Each time I start building a new parser I manage to forget a few ^'s I could either add some code to PPCompositeParserTest>parserInstance to check methods having same-named instance variables, or do the same to the PPCompositeParser itself Stephan

1 0

Issue 920 in moose-technology: Petit parser UI shows only production rules that have an instance variable in the selected class
by moose-technology＠googlecode.com 22 Mar '13

22 Mar '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 920 by norbert.hartl: Petit parser UI shows only production rules that have an instance variable in the selected class http://code.google.com/p/moose-technology/issues/detail?id=920 In the petit parser UI if I select a class I can see all production rules of that class. If I have a derived parser class that does not implement every of the production rules I get only those which are defined in the derived class. It would be good if the pane of the production rules list could show productions from every class in the hierarchie above the petit parser ones. -- 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

Build failed in Jenkins: moose-latest-dev-4.8 #91
by admin＠moosetechnology.org 21 Mar '13

21 Mar '13

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/91/> ------------------------------------------ Started by user tudor(a)tudorgirba.com Building remotely on moose-slave 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/hudson8583979152805326.sh + bash + wget --quiet -O - http://pharo.gforge.inria.fr/ci/script/ciPharo20.sh Downloading the latest 2.0 Image: http://files.pharo.org/image/20/latest.zip Pharo.image Pharo.changes + bash + wget --quiet -O - http://pharo.gforge.inria.fr/ci/script/ciPharoVMLatest.sh Downloading the latest pharoVM: http://files.pharo.org/vm/pharo/linux/pharo-linux-latest.zip vm/pharo Downloading PharoV10.sources: http://files.pharo.org/image//PharoV10.sources.zip Downloading PharoV20.sources: http://files.pharo.org/image//PharoV20.sources.zip Creating starter scripts vm.sh and vm-ui.sh Please install the 32bit libraries sudo aptitude install ia32-libs + ./vm.sh Pharo.image save moose-latest-dev-4.8 + REPO=http://www.smalltalkhub.com/mc/Moose/Moose/main + ./vm.sh 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[31m==== Startup Error: MetacelloProjectSpecLoadError: No version found for #development of ConfigurationOfMondrian [0mMetacelloMCProjectSpec>>loadVersion: MetacelloMCProjectSpec>>load MetacelloProjectReferenceSpec>>loadUsing:gofer: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>linearLoadPackageSpecs:repositories: in Block: [:pkg | pkg loadUsing: self gofer: gofer] OrderedCollection>>do: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>linearLoadPackageSpecs:repositories: MetacelloFetchingMCSpecLoader>>atomicLoadPackageSpecs:repositories: in Block: [super linearLoadPackageSpecs: packageSpecs reposi...etc... BlockClosure>>ensure: MetacelloLoaderPolicy>>pushLoadDirective:during: MetacelloLoaderPolicy>>pushAtomicLoadDirectivesDuring:for: MetacelloFetchingMCSpecLoader>>atomicLoadPackageSpecs:repositories: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>load MetacelloMCVersionSpecLoader>>load MetacelloMCVersion>>executeLoadFromArray: MetacelloMCVersion>>fetchRequiredFromArray: in Block: [:dict | ^ self executeLoadFromArray: anArray] MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: in Block: [^ aBlock value: dict] BlockClosure>>on:do: MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: MetacelloMCVersion>>fetchRequiredFromArray: in Block: [self versionSpec loader: newLoader.... BlockClosure>>ensure: MetacelloMCVersion>>fetchRequiredFromArray: in Block: [[self versionSpec loader: newLoader.... MetacelloPharoPlatform>>do:displaying: in Block: [:bar | ... BlockClosure>>cull: Job>>run in Block: [result := block cull: self] BlockClosure>>on:do: Job>>run in Block: [self prepareForRunning.... BlockClosure>>ensure: Job>>run NonInteractiveUIManager(UIManager)>>displayProgress:from:to:during: ByteString(String)>>displayProgressFrom:to:during: [0m[31mGot startup errors: [0m[31m MetacelloProjectSpecLoadError: No version found for #development of ConfigurationOfMondrian [0mBuild step 'Execute shell' marked build as failure Archiving artifacts Recording test results

3 10

CI down?
by Yuriy Tymchuk 21 Mar '13

21 Mar '13

https://ci.inria.fr/moose 503 error -- View this message in context: http://moose-dev.97923.n3.nabble.com/CI-down-tp4026554.html Sent from the moose-dev mailing list archive at Nabble.com.

1 0

Fwd: [Evol] Call for PhD candidates in the Software Composition Group, U Bern
by Tudor Girba 19 Mar '13

19 Mar '13

---------- Forwarded message ---------- From: Oscar Nierstrasz <oscar(a)iam.unibe.ch> Date: Tue, Mar 19, 2013 at 2:27 PM Subject: [Evol] Call for PhD candidates in the Software Composition Group, U Bern To: evol(a)lists.inf.unisi.ch Applications are invited for PhD candidates at the Software Composition Group, University of Bern, Switzerland. The Software Composition Group carries out research in software analysis and programming language design and implementation, with a view to enabling software evolution. The SCG is led by Prof. Oscar Nierstrasz and is part of the Institute of Computer Science and Applied Mathematics (IAM) at the University of Berne. Details about current and ongoing research can be found here: http://scg.unibe.ch/research/ The candidate must have a MSc in Computer Science (equivalent to a Swiss MSc), should demonstrate strong programming skills, and have research interests in several of the following areas: - software evolution - program understanding - software modeling - model-driven engineering - reverse engineering - domain specific languages - dynamic analysis - integrated development environments - programming language design - virtual machine technology To apply, please send an email including your CV, with references, to Prof. Oscar Nierstrasz (oscar(a)iam.unibe.ch), by April 15, 2013. Oscar Nierstrasz --- Prof. Dr. O. Nierstrasz -- oscar(a)iam.unibe.ch Software Composition Group -- http://scg.unibe.ch/oscar University of Bern -- Tel/Fax +41 31 631.4618/3355 _______________________________________________ Evol mailing list Evol(a)lists.inf.unisi.ch http://lists.inf.unisi.ch/mailman/listinfo/evol -- www.tudorgirba.com "Every thing has its own flow"

1 0

Failing PetitSmalltalk tests
by Yuriy Tymchuk 19 Mar '13

19 Mar '13

Hi. In Pharo 2.0 PetitSmalltalk tests are failing. Firs of all there are real problems with parsing as some test fail because parser finishes to parse before the end of the stream. Right now I don't know what's causing the problem and how to solve it. Then there is a ton of deprecation warnings as PPToken>>#value became deprecated and it's recommended to use #inputValue. It's now hard to fix that, but there are two problems. 1) At places where #value message is sent, not only PPToken is used as a receiver, but sometimes RBToken is used instead. And RBToken does not understand the #inputValue message. This can be hacked by adding a protocol-extension that will return "self value" then, but it's not very nice. 2) Some #value messages are sent from methods in AST-Core package, and I don't know how we should deal with that. Any ideas for solutions? Uko -- View this message in context: http://moose-dev.97923.n3.nabble.com/Failing-PetitSmalltalk-tests-tp4026442… Sent from the moose-dev mailing list archive at Nabble.com.

4 7

moose job on jenkins
by Tudor Girba 19 Mar '13

19 Mar '13

Hi, I put together a little description of how we built the Moose job on Jenkins using the CommandLine infrastructure. Perhaps it is useful for other people as well: http://www.tudorgirba.com/blog/moose-4-8-on-jenkins Cheers, Doru -- www.tudorgirba.com "Be rather willing to give than demanding to get."

4 6

Migrated SmallDude now….
by Stéphane Ducasse 18 Mar '13

18 Mar '13

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev