<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Philippe,<div class=""><br class=""></div><div class="">On Pharo4, the testExceptionHandlerNesting is failing.</div><div class="">It seems that Pharo4 now has the ANSI behavior for exception lookup [3].</div><div class=""><br class=""></div><div class="">Though this test is failing, I still get the expected behavior from WAWalkbackErrorHandler (i.e. opening a debugger on the right spot in the stack). </div><div class="">I think this is because of the workarounds introduced in [1][2].</div><div class=""><br class=""></div><div class="">But then I wonder about what this test is supposed to do: it is now checking for the presence of the non-ANSI lookup behaviour.</div><div class=""><br class=""></div><div class="">Mind that this test also fails on Gemstone, where it was rewritten in a way to not fail.</div><div class="">I was already puzzled by that before actually..</div><div class=""><br class=""></div><div class="">So, what is this failing test supposed to say? :)</div><div class=""><br class=""></div><div class="">[1] <a href="https://code.google.com/p/seaside/issues/detail?id=636" class="">https://code.google.com/p/seaside/issues/detail?id=636</a></div><div class="">[2] <a href="https://github.com/SeasideSt/googlecode-seaside-export/issues/636" class="">https://github.com/SeasideSt/googlecode-seaside-export/issues/636</a></div></body></html>