Issue 4101 in pharo: MessageTally spyOn: returns an invalid incr information

Status: New
Owner: [hidden email]
CC: [hidden email]
Labels: Milestone-1.3 Type-ReportDefect

New issue 4101 by [hidden email]: MessageTally spyOn: returns an  
invalid incr information
http://code.google.com/p/pharo/issues/detail?id=4101

in Pharo 1.3, VM 4.2.5

When I execute for example:
===
MessageTally spyOn:
      [ 500 timesRepeat: [
                      | str |
                      str := ''.
                      9000 timesRepeat: [ str := str, 'A' ]]].
===

The result is:
===
**GCs**
        full 0 totalling 0ms (0.0% uptime)
        incr 7250 totalling 389,048ms (1946.0% uptime), avg 54.0ms
        tenures 0
        root table 0 overflows
===
Here we can see that the incr information is false.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #1 on issue 4101 by [hidden email]: MessageTally spyOn:  
returns an invalid incr information
http://code.google.com/p/pharo/issues/detail?id=4101

Is that a problem just in 1.3 or in 1.2, too?




_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Labels: Milestone-1.2

Comment #2 on issue 4101 by [hidden email]: MessageTally spyOn:  
returns an invalid incr information
http://code.google.com/p/pharo/issues/detail?id=4101

in 1.2 too


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Labels: -Milestone-1.3 -Milestone-1.2

Comment #3 on issue 4101 by [hidden email]: MessageTally spyOn:  
returns an invalid incr information
http://code.google.com/p/pharo/issues/detail?id=4101

As we are late in 1.3, bugs that are in the current release are not show  
stoppers for releasing 1.3, either


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #4 on issue 4101 by [hidden email]: MessageTally spyOn:  
returns an invalid incr information
http://code.google.com/p/pharo/issues/detail?id=4101

jannik can you check if the problem is the same in Squeak and Cuis?


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #5 on issue 4101 by [hidden email]: MessageTally spyOn:  
returns an invalid incr information
http://code.google.com/p/pharo/issues/detail?id=4101

Same in Squeak.
Cuis 3.2 works fine:
==
**GCs**
        full 0 totalling 0ms (0.0% uptime)
        incr 20747 totalling 7,201ms (24.0% uptime), avg 0.0ms
        tenures 0
        root table 0 overflows
==


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #6 on issue 4101 by [hidden email]: MessageTally spyOn: returns  
an invalid incr information
http://code.google.com/p/pharo/issues/detail?id=4101

This is specific to some VMs on the Mac due to change in primitive timing  
precision.

It's easier to just divide mentally by 1000 than introduce checks for the  
specific VM's who do this :)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: Closed

Comment #7 on issue 4101 by [hidden email]: MessageTally spyOn:  
returns an invalid incr information
http://code.google.com/p/pharo/issues/detail?id=4101

With Pharo 2.0 now beta, time has come to review bug reports that have not  
seen any activity in 2012.
To keep the amount of issues managable, we close reports that have not  
drawn any attention for over one
year.

The reporter (and thus owner) of the issue should:

  -> check the issue in 2.0. Is it still relevant?
  -> If yes, just add a note to the report and we will be opened again.


As your issue has not seen any attention for over a year, please consider  
to give more information.
A good idea can be to send a mail to the mailinglist to get other people to  
help fixing the bug or implementing
an improvement.



_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #8 on issue 4101 by [hidden email]: MessageTally spyOn:  
returns an invalid incr information
http://code.google.com/p/pharo/issues/detail?id=4101

I do not really understand the issue. Jannik, on your example, what is  
wrong with the incr info?


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #9 on issue 4101 by [hidden email]: MessageTally spyOn:  
returns an invalid incr information
http://code.google.com/p/pharo/issues/detail?id=4101

it seems to work in 2.0


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #10 on issue 4101 by [hidden email]: MessageTally spyOn:  
returns an invalid incr information
http://code.google.com/p/pharo/issues/detail?id=4101

Good :-)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Labels: MigratedToFogBugz

Comment #11 on issue 4101 by [hidden email]: MessageTally spyOn:  
returns an invalid incr information
http://code.google.com/p/pharo/issues/detail?id=4101#c11

Issue migrated to https://pharo.fogbugz.com/f/cases/4148

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker