search

AutomatedArchitecture / SirenOfShame

Gamification for Continuous Integration
https://sirenofshame.com
GNU General Public License v2.0
71 stars 48 forks source link

TFS has builds that have long since completed as running #39

Open pvandervelde opened 10 years ago

pvandervelde commented 10 years ago

Apparently SoS thinks that we have builds that have been running for over a year now. The image shows what SoS thinks are (some of) our running builds. The first two builds were indeed running according to TFS, the other ones were not.

image

lprichar commented 10 years ago

Sorry for the delay. Do you see anything suspicious in the logs (see screenshot here http://sirenofshame.blogspot.com/2012/01/how-to-report-errors.html)?

pvandervelde commented 10 years ago

I think those logs were eaten when I was trying to figure out what was causing #38. I've turned of SoS until there's a fix for that issue. I might have some time this week to start it up again and see if I can reproduce the issue / attach a debugger / grab the logs etc.

pvandervelde commented 10 years ago

Looking at the debugger trying for issue #38 I just spotted this. One of the builds is 10 months old. I got this information from a breakpoint at the end of MyBuildServer.GetBuildStatuses

{SirenOfShame.Lib.Watcher.BuildStatus} BallIndex Green
BuildDefinitionId "321" BuildId "216612" BuildStatusDescription "Passing"
BuildStatusEnum Working BuildStatusMessage null Comment "Manual" FinishedTime {6/03/2014 01:18:13} LocalStartTime {23/09/2014 15:14:47} Name "MyProj" RequestedBy "Somebody" StartedTime {6/03/2014 01:10:53}

It looks like there is a start and finish time but somehow the buildstatus is working?