15 Apr
2015
15 Apr
'15
7:38 p.m.
Hi!
This is the error I get when I simply open Pharo with Roassal installed.
roassal2.zip <https://ci.inria.fr/moose/job/roassal2/1390/artifact/roassal2.zip>
(https://ci.inria.fr/moose/job/roassal2/1390/artifact/roassal2.zip
<https://ci.inria.fr/moose/job/roassal2/1390/artifact/roassal2.zip>)
I am not sure where this comes from. How can the build succeed by the way?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
15 Apr
15 Apr
10:42 p.m.
Hi,
The jenkins build for roassal 2 loads
ConfigurationsOfRoassal2>>#development into a Pharo 4.0 image.
This just loads Roassal2 without any other package like the inspector
extensions or the GTDebugger.
It seems that this job is only for detecting failing tests in the core of
roassal rather than to produce ready to use images
Cheers,
Andrei
On Wed, Apr 15, 2015 at 7:38 PM, Alexandre Bergel <alexandre.bergel(a)me.com>
wrote:
Hi!
This is the error I get when I simply open Pharo with Roassal installed.
roassal2.zip
<https://ci.inria.fr/moose/job/roassal2/1390/artifact/roassal2.zip> (
https://ci.inria.fr/moose/job/roassal2/1390/artifact/roassal2.zip)
I am not sure where this comes from. How can the build succeed by the way?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
16 Apr
16 Apr
2:02 a.m.
Ok
Thanks
Alexandre
Le 15 avr. 2015 à 17:42, Andrei Chis
<chisvasileandrei(a)gmail.com> a écrit :
Hi,
The jenkins build for roassal 2 loads ConfigurationsOfRoassal2>>#development into a
Pharo 4.0 image.
This just loads Roassal2 without any other package like the inspector extensions or the
GTDebugger.
It seems that this job is only for detecting failing tests in the core of roassal rather
than to produce ready to use images
Cheers,
Andrei
On Wed, Apr 15, 2015 at 7:38 PM, Alexandre Bergel
<alexandre.bergel(a)me.com> wrote:
Hi!
This is the error I get when I simply open Pharo with Roassal installed.
roassal2.zip (https://ci.inria.fr/moose/job/roassal2/1390/artifact/roassal2.zip)
I am not sure where this comes from. How can the build succeed by the way?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev 
7:22 a.m.
Hi,
The issue comes from settings. You saved all settings from a Moose image,
which includes GTGenericStackDebugger and has a setting for it, and then
tried to load those settings in a Roassal2 image that does not contain that
setting.
The settings engine needs reconsideration, but there is not much we can do
now about it.
The simplest thing would be to export again the settings from a basic Pharo
image.
Cheers,
Doru
On Wed, Apr 15, 2015 at 7:38 PM, Alexandre Bergel <alexandre.bergel(a)me.com>
wrote:
Hi!
This is the error I get when I simply open Pharo with Roassal installed.
roassal2.zip
<https://ci.inria.fr/moose/job/roassal2/1390/artifact/roassal2.zip> (
https://ci.inria.fr/moose/job/roassal2/1390/artifact/roassal2.zip)
I am not sure where this comes from. How can the build succeed by the way?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
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"
3:09 p.m.
Ah okay!!!
Thanks! Make sense to me
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Apr 16, 2015, at 2:22 AM, Tudor Girba
<tudor(a)tudorgirba.com> wrote:
Hi,
The issue comes from settings. You saved all settings from a Moose image, which includes
GTGenericStackDebugger and has a setting for it, and then tried to load those settings in
a Roassal2 image that does not contain that setting.
The settings engine needs reconsideration, but there is not much we can do now about it.
The simplest thing would be to export again the settings from a basic Pharo image.
Cheers,
Doru
On Wed, Apr 15, 2015 at 7:38 PM, Alexandre Bergel <alexandre.bergel(a)me.com
<mailto:alexandre.bergel@me.com>> wrote:
Hi!
This is the error I get when I simply open Pharo with Roassal installed.
roassal2.zip <https://ci.inria.fr/moose/job/roassal2/1390/artifact/roassal2.zip>
(https://ci.inria.fr/moose/job/roassal2/1390/artifact/roassal2.zip
<https://ci.inria.fr/moose/job/roassal2/1390/artifact/roassal2.zip>)
I am not sure where this comes from. How can the build succeed by the way?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/>
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
<https://www.iam.unibe.ch/mailman/listinfo/moose-dev>
--
www.tudorgirba.com <http://www.tudorgirba.com/>
"Every thing has its own flow"
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
3583
days inactive
3584
days old
4 comments
3 participants
participants (3)
-
Alexandre Bergel -
Andrei Chis -
Tudor Girba