Moose-dev October 2011

moose-dev@list.inf.unibe.ch

29 participants
175 discussions

Fwd: Build failed in Jenkins: moose-latest-dev #664

by Tudor Girba

Hi Usman, I see that you are hacking on the Lattice. Good :) The Moose build fails becauseyou added an extension to MalLattice in Moose-MondrianPaintings, but when this package gets loaded, the MalLattice is not present. The reason is that ConfigurationOfMooseAlgos does not know about the newly created package: Moose-Algo-Lattice. So, you have to add this package to the ConfigurationOfMooseAlgos>>default: But, before you do that, you should rename the package to Moose-Algos-Lattice. Cheers, Doru ---------- Forwarded message ---------- From: <admin(a)moosetechnology.org> Date: Fri, Oct 21, 2011 at 3:48 PM Subject: Build failed in Jenkins: moose-latest-dev #664 To: tudor(a)tudorgirba.com, simon.denier(a)gmail.com, cy.delaunay(a)gmail.com, alexandre(a)bergel.eu, stephane.ducasse(a)inria.fr, jannik.laval(a)gmail.com See <http://hudson.moosetechnology.org/job/moose-latest-dev/664/> ------------------------------------------ Started by user girba [workspace] $ /bin/sh -xe /tmp/hudson5079168647777384641.sh + rm -rf <http://hudson.moosetechnology.org/job/moose-latest-dev/ws/moose> < http://hudson.moosetechnology.org/job/moose-latest-dev/ws/moose-tests> < http://hudson.moosetechnology.org/job/moose-latest-dev/664/artifact/moose_s… > + /srv/hudson.moosetechnology.org/builder/build.sh -i Pharo-1.3 -s moose -s glamorous-theme -s glamorous-toolkit -s moose-clean -s cleanupforrelease -o moose build.sh: error loading code (/srv/pharo/coglinux2382/squeak) *** Warning: Warning: This package depends on the following classes: MalLattice You must resolve these dependencies before you will be able to load these definitions: MalLattice>>viewLattice: Recording test results Archiving artifacts -- -- www.tudorgirba.com "Every thing has its own flow"

13 years, 2 months

Mondrian: text alignment of popup view

by Veronica Isabel Uquillas Gomez

Hi, When displaying text (e.g. source code) on a popup view, it is all aligned to the left without considering tabs... Stef told that he already fixed this in Morph but using the latest version of Mondrian the problem is still present. What I noticed is that a popup text presents the text correctly. Is some else having the same problem with popup views? Regards, Veronica

13 years, 2 months

Tests FMMetaRepositoryFilterTest

by Andre Hora

Hello, Some tests related to FMMetaRepositoryFilterTest are red in the latest-dev, but when running them in my machine they are green. []'s -- Andre Hora

13 years, 2 months

only one yellow test

by Tudor Girba

Hi, I fixed most tests. As I said before many of the tests failed because the newly defined properties for metrics were not marked as <derived>. The reason why other tests failed was that when we try to load back a model we need a means to set the value. Because most metrics are lazily computable, we do not have setters and thus, they need to be marked with <derived>. The only yellow test is related to RoelTyper which seems to raise again errors in the latest Pharo 1.3. Anyone wants to take this one? :) Cheers, Doru -- www.tudorgirba.com "In a world where everything is moving ever faster, one might have better chances to win by moving slower."

13 years, 2 months

Moose and its configurations

by Alexandre Bergel

Hi! Getting a proper configuration of moose is not easy and probably will not be produced tomorrow. I spent some time with our Metacello Sansei, and we did not fix it. Many cycles from the configuration can be removed by simply removing the dependency on ConfigurationOfMoose. For example, ConfigurationOfDSM, ConfigurationOfKumpel and ConfigurationOfSmallDude explicitly load Moose. Is there a reason for this? Saying that DSM, Kumpel and SmallDude can only be loaded in a Pharo with Moose will simplify the situation in my opinion. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

13 years, 2 months

problems with fuel serializing non-integer numbers

by Tudor Girba

Hi Mariano, hi Martin, As you know, we are using Fuel for serializing objects based on Fame descriptions. We recently added new properties to Fame that contain number values that are not integer (e.g., Float), and now we get the problem that Fuel does not seem to be able to serialize them. To reproduce the problem, you can download the latest moose image and run the FuelMooseTests: http://ci.moosetechnology.org/job/moose-latest-dev/lastSuccessfulBuild/arti… You will see that there are some 44 errors due to looking up values in the dictionary. Could please you take a look and see if the problem is in Fuel or maybe somewhere else? Cheers, Doru -- www.tudorgirba.com "It's not how it is, it is how we see it."

13 years, 2 months

morph renderer

by Esteban Lorenzano

Hi Doru, I coded a specific glamour renderer for morphs (bah... I copied a lot from magritte renderer). The objective is make possible to update morphs when an update is triggered, and I think in the future there will be much more advantages to having it as a complete renderer. I'm attaching the change set. Cheers, Esteban

13 years, 2 months

moose at smalltalks

by Tudor Girba

Hi, FYI, this year, I will end up at Smalltalks and I will be talking about Humane Assessment, Moose and Glamour. Will any of you be around? Cheers, Doru -- www.tudorgirba.com "One cannot do more than one can do."

13 years, 2 months

Issue 729 in moose-technology: inFusion should create default constructors

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: georgega...(a)gmail.com Labels: Type-Defect Priority-Medium Component-ExternalTools New issue 729 by tu...(a)tudorgirba.com: inFusion should create default constructors http://code.google.com/p/moose-technology/issues/detail?id=729 If we have: public class A { public void m() {...} } public class B { public void x() { new A() ... } } We should get an invocation between B::x() and A::A(), where A::A() should be marked as stub.

13 years, 2 months

please use a sentence to describe an issue

by Tudor Girba

Hi, Please use a sentence when naming an issue. Some examples: - A bug entry should try to specify what the wrong behavior is: "Hismo and classhistories" ==> "allClassHistories is not instance of HismoClassHistoryGroup" - An enhancement should specify what the intended behavior should be: "span or size for each column in GLMTablePresentation" ==> "GLMTablePresentation should allow us to set the size of each column" Cheers, Doru -- www.tudorgirba.com "It's not how it is, it is how we see it."

13 years, 2 months

← Newer
1
...
8
9
10
11
12
13
14
...
18
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev October 2011