Hi
I have the evidence that the importing is not extracting well references between classes.
Now I run the moose tests and I see 10 ignored 1 failed 2 errors
Two questions: How can I know which are the ignored tests? Is there anybody besides us working on references and that may have noticed a problem?
I will try to pin it down (now I can reproduce it by hand but I want a test).
Stef
On 22 Nov 2007, at 16:07 , stephane ducasse wrote:
Now I run the moose tests and I see 10 ignored 1 failed 2 errors Two questions: How can I know which are the ignored tests?
Klick on defects, the method are marked with a dark yellow cross.
cheers, AA
I wrote a test and I will check that tomorrow.
Stef
On 22 nov. 07, at 16:07, stephane ducasse wrote:
Hi
I have the evidence that the importing is not extracting well references between classes.
Now I run the moose tests and I see 10 ignored 1 failed 2 errors
Two questions:
How can I know which are the ignored tests?
Is there anybody besides us working on references and that may have noticed a problem?
I will try to pin it down (now I can reproduce it by hand but I want a test).
Stef
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
It seems that I found the reason of this bug: when we inroduced the possibility to merge the class and metaclass we did not pay attention that a class reference would refer to the metaclass and not the class. I will try to write some tests and fix that.
Stef
On 22 nov. 07, at 21:34, Stéphane Ducasse wrote:
I wrote a test and I will check that tomorrow.
Stef
On 22 nov. 07, at 16:07, stephane ducasse wrote:
Hi
I have the evidence that the importing is not extracting well references between classes.
Now I run the moose tests and I see 10 ignored 1 failed 2 errors
Two questions:
How can I know which are the ignored tests?
Is there anybody besides us working on references and that may have noticed a problem?
I will try to pin it down (now I can reproduce it by hand but I want a test).
Stef
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
What is the current state of that class/metaclass issue anyway? Which solution are we currently using?
AA
On 23 Nov 2007, at 9:26 , Stéphane Ducasse wrote:
It seems that I found the reason of this bug: when we inroduced the possibility to merge the class and metaclass we did not pay attention that a class reference would refer to the metaclass and not the class. I will try to write some tests and fix that.
Stef
On 22 nov. 07, at 21:34, Stéphane Ducasse wrote:
I wrote a test and I will check that tomorrow.
Stef
On 22 nov. 07, at 16:07, stephane ducasse wrote:
Hi
I have the evidence that the importing is not extracting well references between classes.
Now I run the moose tests and I see 10 ignored 1 failed 2 errors
Two questions:
How can I know which are the ignored tests?
Is there anybody besides us working on references and that may have noticed a problem?
I will try to pin it down (now I can reproduce it by hand but I want a test).
Stef
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
I would vote for the one that merges the two, cause actually I always remove the metaclasses.
Doru
On Nov 23, 2007, at 3:49 PM, Adrian Kuhn wrote:
What is the current state of that class/metaclass issue anyway? Which solution are we currently using?
AA
On 23 Nov 2007, at 9:26 , Stéphane Ducasse wrote:
It seems that I found the reason of this bug: when we inroduced the possibility to merge the class and metaclass we did not pay attention that a class reference would refer to the metaclass and not the class. I will try to write some tests and fix that.
Stef
On 22 nov. 07, at 21:34, Stéphane Ducasse wrote:
I wrote a test and I will check that tomorrow.
Stef
On 22 nov. 07, at 16:07, stephane ducasse wrote:
Hi
I have the evidence that the importing is not extracting well references between classes.
Now I run the moose tests and I see 10 ignored 1 failed 2 errors
Two questions:
How can I know which are the ignored tests?
Is there anybody besides us working on references and that may have noticed a problem?
I will try to pin it down (now I can reproduce it by hand but I want a test).
Stef
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com www.tudorgirba.com/blog
"Being happy is a matter of choice."
In fact after losing a couple of hours :( I noticed that there is no bug and that the bug was already coveed by one my old tests. In fact this is the importer of another tests that did not set importer importingContext mergeClassAndMetaclass
So I would put that by default in the Smalltalk importer because this is cool that way.
Stef
On 23 nov. 07, at 16:43, Tudor Girba wrote:
I would vote for the one that merges the two, cause actually I always remove the metaclasses.
Doru
On Nov 23, 2007, at 3:49 PM, Adrian Kuhn wrote:
What is the current state of that class/metaclass issue anyway? Which solution are we currently using?
AA
On 23 Nov 2007, at 9:26 , Stéphane Ducasse wrote:
It seems that I found the reason of this bug: when we inroduced the possibility to merge the class and metaclass we did not pay attention that a class reference would refer to the metaclass and not the class. I will try to write some tests and fix that.
Stef
On 22 nov. 07, at 21:34, Stéphane Ducasse wrote:
I wrote a test and I will check that tomorrow.
Stef
On 22 nov. 07, at 16:07, stephane ducasse wrote:
Hi
I have the evidence that the importing is not extracting well references between classes.
Now I run the moose tests and I see 10 ignored 1 failed 2 errors
Two questions:
How can I know which are the ignored tests?
Is there anybody besides us working on references and that may have noticed a problem?
I will try to pin it down (now I can reproduce it by hand but I want a test).
Stef
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com www.tudorgirba.com/blog
"Being happy is a matter of choice."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-
Adrian Kuhn -
stephane ducasse -
Stéphane Ducasse -
Tudor Girba