Issue 5608 in pharo: ReleaseTest #testObsoleteClasses fails

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Issue 5608 in pharo: ReleaseTest #testObsoleteClasses fails

pharo
Status: FailingTest
Owner: [hidden email]
Labels: Type-Bug Milestone-1.4

New issue 5608 by [hidden email]: ReleaseTest #testObsoleteClasses  
fails
http://code.google.com/p/pharo/issues/detail?id=5608

Obsolete classes remaining: an Array(AnObsoleteReference)

But the when I download the image and run ReleaseTest, it is green


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 5608 in pharo: ReleaseTest #testObsoleteClasses fails

pharo

Comment #1 on issue 5608 by [hidden email]: ReleaseTest  
#testObsoleteClasses fails
http://code.google.com/p/pharo/issues/detail?id=5608

maybe we should recompile the image


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 5608 in pharo: ReleaseTest #testObsoleteClasses fails

pharo

Comment #2 on issue 5608 by [hidden email]: ReleaseTest  
#testObsoleteClasses fails
http://code.google.com/p/pharo/issues/detail?id=5608

This is really strange... if I run this test in the image that is used for  
the test run, it's green.

If I run the test in the image that is saved *after* running the tests, it  
is green.

I really have no clue at all why jenkins sees a failing test.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 5608 in pharo: ReleaseTest #testObsoleteClasses fails

pharo

Comment #3 on issue 5608 by [hidden email]: ReleaseTest  
#testObsoleteClasses fails
http://code.google.com/p/pharo/issues/detail?id=5608

I've seen this too.  I think there is something in the image that is  
hanging on to Reference, but (somehow) gets cleaned up during startup or  
GUI initialisation.

If I run "PointerExplorer openOn: (SystemNavigation default obsoleteClasses  
first)" in a startup script, I get an explorer window with a few  
references, but I can't explore any further as the references are cleaned  
up by the time the GUI starts displaying/responding :(

I've attached a script that opens a PointerExplorer and expands all the  
elements to a particular level.  Change the 5 to whatever you want.  Note  
that numbers > 5 take loooooong on my computer.  Hopefully you have  
something faster.

Also, note the #OnceOnly wrapper in the script - startup scripts are  
currently being run 8 times for me (on Linux), but I'll submit another  
issue for that once I have it characterised better.

Attachments:
        test2.st  406 bytes


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 5608 in pharo: ReleaseTest #testObsoleteClasses fails

pharo
Updates:
        Status: Closed

Comment #4 on issue 5608 by [hidden email]: ReleaseTest  
#testObsoleteClasses fails
http://code.google.com/p/pharo/issues/detail?id=5608

I downloaded the build, opened and saved the image and used that --> bug  
disappears


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