Issue 4559 in pharo: Broken test: MethodContextTest>>testClosureRestart

Status: Accepted
Owner: renggli
Labels: Milestone-1.3

New issue 4559 by renggli: Broken test:  
MethodContextTest>>testClosureRestart
http://code.google.com/p/pharo/issues/detail?id=4559

MethodContextTest>>testClosureRestart crashes Cog in headless mode.

MethodContextTest>>testClosureRestart opens a debugger when run normally.


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

Updates:
        Status: ReviewNeeded

Comment #1 on issue 4559 by [hidden email]: Broken test:  
MethodContextTest>>testClosureRestart
http://code.google.com/p/pharo/issues/detail?id=4559

This is already addressed with update #14061.
See
http://code.google.com/p/pharo/issues/detail?id=4555

Since you marked it as 1.3 milestone, should we also integrate this into  
1.3?




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

Comment #2 on issue 4559 by renggli: Broken test:  
MethodContextTest>>testClosureRestart
http://code.google.com/p/pharo/issues/detail?id=4559

Yeah, I would say so. Otherwise it is impossible to run the tests from a in  
Pharo 1.3, and one has to patch out the method when building images  
automatically.


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

Comment #3 on issue 4559 by [hidden email]: Broken test:  
MethodContextTest>>testClosureRestart
http://code.google.com/p/pharo/issues/detail?id=4559

ok, I will add it. This should than solve Issue 4495, too.

(I will do a 1.3 update session today...)


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

Comment #4 on issue 4559 by [hidden email]: Broken test:  
MethodContextTest>>testClosureRestart
http://code.google.com/p/pharo/issues/detail?id=4559

i doubt that it is related (Issue 4495, btw how did you put a link to it?).  
my fix curing exception handling for a single method in testcase which runs  
a block in forked process.
if there's something which enters endless loop while running the test (and  
without forking), it will still behave as before.


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

Comment #5 on issue 4559 by [hidden email]: Broken test:  
MethodContextTest>>testClosureRestart
http://code.google.com/p/pharo/issues/detail?id=4559

Ah, ok... the link appears automatically when writing Issue 4495  
(intelligent tracker...)


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

Comment #6 on issue 4559 by renggli: Broken test:  
MethodContextTest>>testClosureRestart
http://code.google.com/p/pharo/issues/detail?id=4559

I reopened Issue 14061, because I think the fix duplicates behavior and  
does not address the problem well enough.


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

Comment #7 on issue 4559 by renggli: Broken test:  
MethodContextTest>>testClosureRestart
http://code.google.com/p/pharo/issues/detail?id=4559

I reopened Issue 4495, because I think the fix duplicates behavior and does  
not address the problem well enough.


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

Comment #8 on issue 4559 by renggli: Broken test:  
MethodContextTest>>testClosureRestart
http://code.google.com/p/pharo/issues/detail?id=4559

I reopened Issue 4555, because I think the fix duplicates behavior and does  
not address the problem well enough.


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

Updates:
        Status: Duplicate
        Mergedinto: 4555

Comment #9 on issue 4559 by [hidden email]: Broken test:  
MethodContextTest>>testClosureRestart
http://code.google.com/p/pharo/issues/detail?id=4559

Ok, so I tag the other issue for 1.3 and merge this report in the other


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