28 Jun
2010
28 Jun
'10
5:26 p.m.
Before posting this issue on pharo, I would like to check that I'm not the only one
affected.
On my computer, some tests of Moose-Algos-Graph are failing since we went to Pharo 1.1.
Same things for our internal test server (they do not appear on hudson though, maybe
because hudson does not test moose-algos?)
This was really strange until I noticed that some data structures used by MooseAlgos were
missing their trait declaration.
I have something like that in monticello:
MOGraphNode subclass: #MABfsNode
uses: MATEdgeNode - {#previousEdges. #from:edge:}
instanceVariableNames: 'nextEdges firstDepth'
classVariableNames: ''
poolDictionaries: ''
category: 'Moose-Algos-Graph'
But when loading the package, the definition becomes:
MOGraphNode subclass: #MABfsNode
instanceVariableNames: 'nextEdges firstDepth'
classVariableNames: ''
poolDictionaries: ''
category: 'Moose-Algos-Graph'
Notice that the trait declaration is missing, but it seems to only happen when the
declaration contains an operation like #-
A declaration without operator loads fine:
MOGraphNode subclass: #MADijkstraNode
uses: MATEdgeNode
instanceVariableNames: 'pathWeight previousEdges nextEdges previousNodes'
classVariableNames: ''
poolDictionaries: ''
category: 'Moose-Algos-Graph'
Can anyone confirm? Because it seems like a strong bug and I'm surprised nobody
noticed it before.
--
Simon
28 Jun
28 Jun
7:50 p.m.
Hi Simon,
I cannot reproduce it.
The Hudson server is running the MooseAlgos tests. If you want to look
at the image, just download it:
http://hudson.moosetechnology.org/job/moose-latest-dev/lastSuccessfulBuild/…
I also just tried to build the image locally, and it worked just well.
This is what I get:
MOGraphNode subclass: #MABfsNode
uses: MATEdgeNode - {#previousEdges. #from:edge:}
instanceVariableNames: 'nextEdges firstDepth'
classVariableNames: ''
poolDictionaries: ''
category: 'Moose-Algos-Graph'
Doru
On 28 Jun 2010, at 17:26, Simon Denier wrote:
Before posting this issue on pharo, I would like to
check that I'm
not the only one affected.
On my computer, some tests of Moose-Algos-Graph are failing since we
went to Pharo 1.1. Same things for our internal test server (they do
not appear on hudson though, maybe because hudson does not test
moose-algos?)
This was really strange until I noticed that some data structures
used by MooseAlgos were missing their trait declaration.
I have something like that in monticello:
MOGraphNode subclass: #MABfsNode
uses: MATEdgeNode - {#previousEdges. #from:edge:}
instanceVariableNames: 'nextEdges firstDepth'
classVariableNames: ''
poolDictionaries: ''
category: 'Moose-Algos-Graph'
But when loading the package, the definition becomes:
MOGraphNode subclass: #MABfsNode
instanceVariableNames: 'nextEdges firstDepth'
classVariableNames: ''
poolDictionaries: ''
category: 'Moose-Algos-Graph'
Notice that the trait declaration is missing, but it seems to only
happen when the declaration contains an operation like #-
A declaration without operator loads fine:
MOGraphNode subclass: #MADijkstraNode
uses: MATEdgeNode
instanceVariableNames: 'pathWeight previousEdges nextEdges
previousNodes'
classVariableNames: ''
poolDictionaries: ''
category: 'Moose-Algos-Graph'
Can anyone confirm? Because it seems like a strong bug and I'm
surprised nobody noticed it before.
--
Simon
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Obvious things are difficult to teach."
8:23 p.m.
This is really strange. I have this bug in all my 1.1 images with moose.
Which image version do you have? Did you load a pharo dev, OB, O2?...
On 28 juin 2010, at 19:50, Tudor Girba wrote:
Hi Simon,
I cannot reproduce it.
The Hudson server is running the MooseAlgos tests. If you want to look at the image, just
download it:
http://hudson.moosetechnology.org/job/moose-latest-dev/lastSuccessfulBuild/…
I also just tried to build the image locally, and it worked just well. This is what I
get:
MOGraphNode subclass: #MABfsNode
uses: MATEdgeNode - {#previousEdges. #from:edge:}
instanceVariableNames: 'nextEdges firstDepth'
classVariableNames: ''
poolDictionaries: ''
category: 'Moose-Algos-Graph'
Doru
On 28 Jun 2010, at 17:26, Simon Denier wrote:
--
Simon
Before posting this issue on pharo, I would like
to check that I'm not the only one affected.
On my computer, some tests of Moose-Algos-Graph are failing since we went to Pharo 1.1.
Same things for our internal test server (they do not appear on hudson though, maybe
because hudson does not test moose-algos?)
This was really strange until I noticed that some data structures used by MooseAlgos were
missing their trait declaration.
I have something like that in monticello:
MOGraphNode subclass: #MABfsNode
uses: MATEdgeNode - {#previousEdges. #from:edge:}
instanceVariableNames: 'nextEdges firstDepth'
classVariableNames: ''
poolDictionaries: ''
category: 'Moose-Algos-Graph'
But when loading the package, the definition becomes:
MOGraphNode subclass: #MABfsNode
instanceVariableNames: 'nextEdges firstDepth'
classVariableNames: ''
poolDictionaries: ''
category: 'Moose-Algos-Graph'
Notice that the trait declaration is missing, but it seems to only happen when the
declaration contains an operation like #-
A declaration without operator loads fine:
MOGraphNode subclass: #MADijkstraNode
uses: MATEdgeNode
instanceVariableNames: 'pathWeight previousEdges nextEdges previousNodes'
classVariableNames: ''
poolDictionaries: ''
category: 'Moose-Algos-Graph'
Can anyone confirm? Because it seems like a strong bug and I'm surprised nobody
noticed it before.
--
Simon
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Obvious things are difficult to teach."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
8:34 p.m.
Hi,
I use Pharo-1.1-11367-Betadev10.05.1.
Doru
On 28 Jun 2010, at 20:23, Simon Denier wrote:
This is really strange. I have this bug in all my 1.1 images with
moose.
Which image version do you have? Did you load a pharo dev, OB, O2?...
On 28 juin 2010, at 19:50, Tudor Girba wrote:
--
www.tudorgirba.com
"Not knowing how to do something is not an argument for how it cannot
be done."
Hi Simon,
I cannot reproduce it.
The Hudson server is running the MooseAlgos tests. If you want to
look at the image, just download it:
http://hudson.moosetechnology.org/job/moose-latest-dev/lastSuccessfulBuild/…
I also just tried to build the image locally, and it worked just
well. This is what I get:
MOGraphNode subclass: #MABfsNode
uses: MATEdgeNode - {#previousEdges. #from:edge:}
instanceVariableNames: 'nextEdges firstDepth'
classVariableNames: ''
poolDictionaries: ''
category: 'Moose-Algos-Graph'
Doru
On 28 Jun 2010, at 17:26, Simon Denier wrote:
--
Simon
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev Before posting this issue on pharo, I would like
to check that I'm
not the only one affected.
On my computer, some tests of Moose-Algos-Graph are failing since
we went to Pharo 1.1. Same things for our internal test server
(they do not appear on hudson though, maybe because hudson does
not test moose-algos?)
This was really strange until I noticed that some data structures
used by MooseAlgos were missing their trait declaration.
I have something like that in monticello:
MOGraphNode subclass: #MABfsNode
uses: MATEdgeNode - {#previousEdges. #from:edge:}
instanceVariableNames: 'nextEdges firstDepth'
classVariableNames: ''
poolDictionaries: ''
category: 'Moose-Algos-Graph'
But when loading the package, the definition becomes:
MOGraphNode subclass: #MABfsNode
instanceVariableNames: 'nextEdges firstDepth'
classVariableNames: ''
poolDictionaries: ''
category: 'Moose-Algos-Graph'
Notice that the trait declaration is missing, but it seems to only
happen when the declaration contains an operation like #-
A declaration without operator loads fine:
MOGraphNode subclass: #MADijkstraNode
uses: MATEdgeNode
instanceVariableNames: 'pathWeight previousEdges nextEdges
previousNodes'
classVariableNames: ''
poolDictionaries: ''
category: 'Moose-Algos-Graph'
Can anyone confirm? Because it seems like a strong bug and I'm
surprised nobody noticed it before.
--
Simon
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Obvious things are difficult to teach."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
8:41 p.m.
On 28 juin 2010, at 20:34, Tudor Girba wrote:
Hi,
I use Pharo-1.1-11367-Betadev10.05.1.
ok
I have the bug with 11383 and 11400-rc2.
Can you check?
Doru
On 28 Jun 2010, at 20:23, Simon Denier wrote:
--
Simon
This is really strange. I have this bug in all my 1.1 images with moose.
Which image version do you have? Did you load a pharo dev, OB, O2?...
On 28 juin 2010, at 19:50, Tudor Girba wrote:
--
www.tudorgirba.com
"Not knowing how to do something is not an argument for how it cannot be
done."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev Hi Simon,
I cannot reproduce it.
The Hudson server is running the MooseAlgos tests. If you want to look at the image, just
download it:
http://hudson.moosetechnology.org/job/moose-latest-dev/lastSuccessfulBuild/…
I also just tried to build the image locally, and it worked just well. This is what I
get:
MOGraphNode subclass: #MABfsNode
uses: MATEdgeNode - {#previousEdges. #from:edge:}
instanceVariableNames: 'nextEdges firstDepth'
classVariableNames: ''
poolDictionaries: ''
category: 'Moose-Algos-Graph'
Doru
On 28 Jun 2010, at 17:26, Simon Denier wrote:
--
Simon
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev Before posting this issue on pharo, I would like
to check that I'm not the only one affected.
On my computer, some tests of Moose-Algos-Graph are failing since we went to Pharo 1.1.
Same things for our internal test server (they do not appear on hudson though, maybe
because hudson does not test moose-algos?)
This was really strange until I noticed that some data structures used by MooseAlgos were
missing their trait declaration.
I have something like that in monticello:
MOGraphNode subclass: #MABfsNode
uses: MATEdgeNode - {#previousEdges. #from:edge:}
instanceVariableNames: 'nextEdges firstDepth'
classVariableNames: ''
poolDictionaries: ''
category: 'Moose-Algos-Graph'
But when loading the package, the definition becomes:
MOGraphNode subclass: #MABfsNode
instanceVariableNames: 'nextEdges firstDepth'
classVariableNames: ''
poolDictionaries: ''
category: 'Moose-Algos-Graph'
Notice that the trait declaration is missing, but it seems to only happen when the
declaration contains an operation like #-
A declaration without operator loads fine:
MOGraphNode subclass: #MADijkstraNode
uses: MATEdgeNode
instanceVariableNames: 'pathWeight previousEdges nextEdges previousNodes'
classVariableNames: ''
poolDictionaries: ''
category: 'Moose-Algos-Graph'
Can anyone confirm? Because it seems like a strong bug and I'm surprised nobody
noticed it before.
--
Simon
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Obvious things are difficult to teach."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev 
9:31 p.m.
strange
let me know if you identify the problem
Stef
On Jun 28, 2010, at 8:23 PM, Simon Denier wrote:
This is really strange. I have this bug in all my 1.1 images with moose.
Which image version do you have? Did you load a pharo dev, OB, O2?...
On 28 juin 2010, at 19:50, Tudor Girba wrote:
Hi Simon,
I cannot reproduce it.
The Hudson server is running the MooseAlgos tests. If you want to look at the image, just
download it:
http://hudson.moosetechnology.org/job/moose-latest-dev/lastSuccessfulBuild/…
I also just tried to build the image locally, and it worked just well. This is what I
get:
MOGraphNode subclass: #MABfsNode
uses: MATEdgeNode - {#previousEdges. #from:edge:}
instanceVariableNames: 'nextEdges firstDepth'
classVariableNames: ''
poolDictionaries: ''
category: 'Moose-Algos-Graph'
Doru
On 28 Jun 2010, at 17:26, Simon Denier wrote:
--
Simon
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev Before posting this issue on pharo, I would like
to check that I'm not the only one affected.
On my computer, some tests of Moose-Algos-Graph are failing since we went to Pharo 1.1.
Same things for our internal test server (they do not appear on hudson though, maybe
because hudson does not test moose-algos?)
This was really strange until I noticed that some data structures used by MooseAlgos were
missing their trait declaration.
I have something like that in monticello:
MOGraphNode subclass: #MABfsNode
uses: MATEdgeNode - {#previousEdges. #from:edge:}
instanceVariableNames: 'nextEdges firstDepth'
classVariableNames: ''
poolDictionaries: ''
category: 'Moose-Algos-Graph'
But when loading the package, the definition becomes:
MOGraphNode subclass: #MABfsNode
instanceVariableNames: 'nextEdges firstDepth'
classVariableNames: ''
poolDictionaries: ''
category: 'Moose-Algos-Graph'
Notice that the trait declaration is missing, but it seems to only happen when the
declaration contains an operation like #-
A declaration without operator loads fine:
MOGraphNode subclass: #MADijkstraNode
uses: MATEdgeNode
instanceVariableNames: 'pathWeight previousEdges nextEdges previousNodes'
classVariableNames: ''
poolDictionaries: ''
category: 'Moose-Algos-Graph'
Can anyone confirm? Because it seems like a strong bug and I'm surprised nobody
noticed it before.
--
Simon
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Obvious things are difficult to teach."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
9:54 p.m.
Hi,
Ok, I could reproduce the problem in Pharo-1.1-11400-rc2dev10.06.1.
Cheers,
Doru
On 28 Jun 2010, at 21:31, Stéphane Ducasse wrote:
strange
let me know if you identify the problem
Stef
On Jun 28, 2010, at 8:23 PM, Simon Denier wrote:
--
www.tudorgirba.com
"Every thing should have the right to be different."
This is really strange. I have this bug in all my 1.1 images with
moose.
Which image version do you have? Did you load a pharo dev, OB, O2?...
On 28 juin 2010, at 19:50, Tudor Girba wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev Hi Simon,
I cannot reproduce it.
The Hudson server is running the MooseAlgos tests. If you want to
look at the image, just download it:
http://hudson.moosetechnology.org/job/moose-latest-dev/lastSuccessfulBuild/…
I also just tried to build the image locally, and it worked just
well. This is what I get:
MOGraphNode subclass: #MABfsNode
uses: MATEdgeNode - {#previousEdges. #from:edge:}
instanceVariableNames: 'nextEdges firstDepth'
classVariableNames: ''
poolDictionaries: ''
category: 'Moose-Algos-Graph'
Doru
On 28 Jun 2010, at 17:26, Simon Denier wrote:
--
Simon
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev Before posting this issue on pharo, I would like
to check that
I'm not the only one affected.
On my computer, some tests of Moose-Algos-Graph are failing since
we went to Pharo 1.1. Same things for our internal test server
(they do not appear on hudson though, maybe because hudson does
not test moose-algos?)
This was really strange until I noticed that some data structures
used by MooseAlgos were missing their trait declaration.
I have something like that in monticello:
MOGraphNode subclass: #MABfsNode
uses: MATEdgeNode - {#previousEdges. #from:edge:}
instanceVariableNames: 'nextEdges firstDepth'
classVariableNames: ''
poolDictionaries: ''
category: 'Moose-Algos-Graph'
But when loading the package, the definition becomes:
MOGraphNode subclass: #MABfsNode
instanceVariableNames: 'nextEdges firstDepth'
classVariableNames: ''
poolDictionaries: ''
category: 'Moose-Algos-Graph'
Notice that the trait declaration is missing, but it seems to
only happen when the declaration contains an operation like #-
A declaration without operator loads fine:
MOGraphNode subclass: #MADijkstraNode
uses: MATEdgeNode
instanceVariableNames: 'pathWeight previousEdges nextEdges
previousNodes'
classVariableNames: ''
poolDictionaries: ''
category: 'Moose-Algos-Graph'
Can anyone confirm? Because it seems like a strong bug and I'm
surprised nobody noticed it before.
--
Simon
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Obvious things are difficult to teach."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
5049
days inactive
5049
days old
6 comments
3 participants
participants (3)
-
Simon Denier -
Stéphane Ducasse -
Tudor Girba