Incorrect balloon message "regressed" following clean build

What steps will reproduce the problem?
1. Tell Hudson-Tray to monitor a hudson build that's currently "green".
2. Start a build from Hudson's web-UI.
3. Abort it.
4. Start another build of that project and let it run to completion.

What is the expected output? What do you see instead?
I expected either
 - to see that the project was in an unknown state (due to the aborted build) until the project had rebuilt successfully, or
 - to see no effect at all until Hudson knew whether the build had worked or not
What I actually saw was nothing until the second build had completed, at which 
point there was a baloon pop-up (from Hudson-Tray) telling me that my build had 
"regressed".  My build had not regressed - it was perfectly healthy.

What version of the product are you using? On what operating system?
Version 0.11.1.0, running on Windows 7, talking to Hudson 1.373 that's on Win 
XP Pro.

Please provide any additional information below.

In my opinion, a sequence of green -> aborted/unknown -> green should not 
trigger a "regressed" balloon pop-up at any point, as the build had not 
regressed.  One should *not* get any complaint from Hudson-Tray that declares 
that all is not well if all is well.
Personally, I would expect aborted builds to be largely ignored by Hudson-Tray.

Original issue reported on code.google.com by pjdar...@gmail.com on 2 Sep 2010 at 12:44

adam-may / hudson-tray-tracker

Incorrect balloon message "regressed" following clean build #56