Hello,

Today I experimented some strange behaviours with announcements that I didn't have in some previous moose images. 
I think that there was some changes related to announcements in pharo recently, but I could not be sure it is related.

At one point in my code I have:

browser on: AnnouncementClass send: #actionSelector
browser announce: anAnnouncementClass.
....
....

I have the feeling that sometimes #actionSelector is executed asynchronously from the rest the code below 'browser announce: ...' .
Not sure but there is maybe something with exception signals. If any signal is emited in #actionSelector it will not execute the rest of the method.

I was at leat able to write a test that do not pass in latest dev

Gofer new
squeaksource: 'DelaunayTmpStuffs';
package: 'ExampleAnnouncementProblems';
load.


will not pass with: http://ci.moosetechnology.org/job/moose-latest-dev/402/artifact/moose_suite-4_5_dev.zip
will pass with: http://ci.moosetechnology.org/job/moose-latest-dev/393/artifact/moose_suite-4_5_dev.zip