Re: [Pharo-project] ECUntypedModelTest >> testNarrowWith failing
On Sun, Sep 26, 2010 at 6:58 PM, Romain Robbes <romain.robbes@gmail.com>wrote:
This one of the tests that were inherited from ECompletion I believe ... I don't really know what to do with them.
Same for your other email actually, although I seem to remember it used to take a normal amount of time, maybe the implementation of some method changed for the worse?
I remember there was some slowdown in certain type of collections in Pharo 1.1. I don't know if hashed, or sorted, weak...I don't know. Maybe it is something related to that? Thanks Mariano
Romain
On Sun, Sep 26, 2010 at 6:32 PM, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
This fails where it does:
self assert: count == model entries size. self assert: count > 100.
since model entries size -> 85
Of course, if I change the test to
self assert: count == model entries size. self assert: count > 80.
it works :)
Romain ?
thanks
mariano
On Sun, Sep 26, 2010 at 7:09 PM, Mariano Martinez Peck < marianopeck@gmail.com> wrote:
On Sun, Sep 26, 2010 at 6:58 PM, Romain Robbes <romain.robbes@gmail.com>wrote:
This one of the tests that were inherited from ECompletion I believe ... I don't really know what to do with them.
Same for your other email actually, although I seem to remember it used to take a normal amount of time, maybe the implementation of some method changed for the worse?
I remember there was some slowdown in certain type of collections in Pharo 1.1. I don't know if hashed, or sorted, weak...I don't know. Maybe it is something related to that?
Ups...sorry this answer was to the other email..the one of the time... for this one, I have no idea. MAybe just chaning it to 80 is ok :) Or maybe Lukas can explain us. Cheers Mariano
Thanks
Mariano
Romain
On Sun, Sep 26, 2010 at 6:32 PM, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
This fails where it does:
self assert: count == model entries size. self assert: count > 100.
since model entries size -> 85
Of course, if I change the test to
self assert: count == model entries size. self assert: count > 80.
it works :)
Romain ?
thanks
mariano
I cannot reproduce the problems with ECompletion. Lukas 2010/9/26 Mariano Martinez Peck <marianopeck@gmail.com>:
On Sun, Sep 26, 2010 at 7:09 PM, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
On Sun, Sep 26, 2010 at 6:58 PM, Romain Robbes <romain.robbes@gmail.com> wrote:
This one of the tests that were inherited from ECompletion I believe ... I don't really know what to do with them.
Same for your other email actually, although I seem to remember it used to take a normal amount of time, maybe the implementation of some method changed for the worse?
I remember there was some slowdown in certain type of collections in Pharo 1.1. I don't know if hashed, or sorted, weak...I don't know. Maybe it is something related to that?
Ups...sorry this answer was to the other email..the one of the time...
for this one, I have no idea. MAybe just chaning it to 80 is ok :)
Or maybe Lukas can explain us.
Cheers
Mariano
Thanks
Mariano
  Romain
On Sun, Sep 26, 2010 at 6:32 PM, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
This fails where it does:
self assert: count == model entries size. Â Â Â self assert: count > 100.
since model entries size -> 85
Of course, if I change the test to
self assert: count == model entries size. Â Â Â self assert: count > 80.
it works :)
Romain ?
thanks
mariano
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Lukas Renggli www.lukas-renggli.ch
participants (2)
-
Lukas Renggli -
Mariano Martinez Peck