Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

Start a nNew thread

Jenkins build became unstable: moose-latest-dev-4.8 #1165

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/1165/>

11 years, 7 months

Confused by ConfigurationOfGrease

by Stéphane Ducasse

Hi in my project I defined on Pharo2.0 I did project: 'Grease Core' with: [ spec className: 'ConfigurationOfGrease'; loads: #('Core' ); file: 'ConfigurationOfGrease'; repository: 'http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main' ]; Now it loads Grease-Core.pmm.76 and not Name: Grease-Core-MattSpr.77 which correctly handles trim extension.. I tried (ConfigurationOfGrease project version: #stable) record a MetacelloNullRecordingMCSpecLoader(linear load : linear load : 1.0.8 [ConfigurationOfGrease] load : ConfigurationOfRefactoringBrowser linear load : 1.0.8 [ConfigurationOfGrease] load : Grease-Core-pmm.72 load : Grease-Pharo20-Core-pmm.1 load : Grease-Slime-topa.15) So I thought that it woudl be better. I tried so change my configuration to load the "stable" version project: 'Grease Core' with: [ spec className: 'ConfigurationOfGrease'; loads: #('Core' ); versionString: #stable; file: 'ConfigurationOfGrease'; repository: 'http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main' ]; and it crashed on me. Grease-Pharo20-Core.pmm.1 GRDelegatingStream is not there. So is there a version loading well (without dirty packages) in Pharo2.0? I tried to use the development version and I still dirty packages……. Thanks Stef

11 years, 7 months

Testing moose (roassal)

by Diego Lont

Hi all, We are checking the build server for failed tests, checking what the problem is: I found problems in Glamour. It used a wrong symbol in its configuration, that caused CollectionExtensions not to load. It caused test fails in GToolkit. I found problems with method categories. There are some tests, that are more or less roassal tests, or at least use roassal, so do not belong in Moose-Algos. I think some methods should be moved to *roassal-paintings … or maybe *roassal-moose-algos and the tests should move along with them. I cannot write in roassal, if someone gives me a good method category and write access to roassal, I will move these methods. I found failed tests in Orion, but it looks like we caused them with our change in moose entity, so I will take a closer look and fix it, or write another mail. Cheers, Stephan and Diego

11 years, 7 months

Jenkins build became unstable: moose-latest-dev-4.8 #1153

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/1153/>

11 years, 7 months

Jenkins build became unstable: moose-latest-dev-4.8 #1151

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/1151/>

11 years, 7 months

Initial size of MooseGroupRuntimeStorage?

by Stephan Eggermont

MooseGroupRuntimeStorage >initialize: capacity byType := Dictionary new: 24. byName := IdentityDictionary new: 10000. elements := OrderedCollection new: capacity byName seems a bit excessive/inflexible. Stephan

11 years, 7 months

Re: Testing moose (roassal)

by Stephan Eggermont

Alexandre wrote: > Problem: Some packages related to the Algorithm have wrongly packaged dependencies. This create problem when these algos are loaded and not Roassal. > > A solution to this problem: > 1 - I've open a Moose panel, imported all the packages that match *Algo* and *Roassal-* > 2 - Open a Roassal easel on the model packages and do it the following visualization: Beautiful! I've learned something today. Stephan

11 years, 7 months

Jenkins build became unstable: moose-latest-dev-4.8 #1145

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/1145/>

11 years, 7 months

GraphET x-axis label - bug?

by Usman Bhatti

Hello, I am starting to use GraphET and looks really nice. While learning to script with it, I stumbled upon this script that does not place x-axis label in the correct place. In fact the x-axis label is superimposed on y-axis one. Here's how you can reproduce it: tmpBrowser := GLMDashboard new. tmpBrowser addPaneNamed: #first. tmpBrowser transmit to: #first; andShow: [:a | a graphET title: 'First Chart with ET'; chart: [:chart :mooseModel| chart verticalBarDiagram models: (1 to: 3); xAxisLabel: 'Test label'; yAxisLabel: 'Another'; regularAxis. ]. ]. tmpBrowser openOn: 1

11 years, 7 months

Duplicate packages

by Diego Lont

Hi All, I found a stray package "collectionextensions" version 32 in the moose repository, while the most recent (and referenced in the configuration) package is version 34 in the folder Moose/CollectionExtensions. Any objections if I remove this package? Cheers, Diego

11 years, 7 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev