Issue Details (XML | Word | Printable)

Key: BAM-351
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Edwin Wong [Atlassian]
Reporter: Riaz Khanmohamed
Votes: 0
Watchers: 0
Operations

Add/Edit UI Mockup to this issue
If you were logged in you would be able to see more operations.
Bamboo

build timer incorrect

Created: 18/Oct/06 04:34 AM   Updated: 02/Nov/06 02:47 AM
Component/s: Build Process
Affects Version/s: 0.5.2
Fix Version/s: 0.6

Time Tracking:
Original Estimate: 4 hours
Original Estimate - 4 hours
Remaining Estimate: 4 hours
Remaining Estimate - 4 hours
Time Spent: Not Specified
Remaining Estimate - 4 hours

Participants: Edwin Wong [Atlassian], Mark Chaimungkalanont [Atlassian] and Riaz Khanmohamed
Since last comment: 2 years, 3 weeks ago
Number of comments: 5
Labels:


 Description  « Hide
Not sure how your average time thing works. Since I used the old beetlejuice files, I think it might be incorrect.

I've removed all 'failed' builds that marked themselves as successful. Looking through every build in the results page, the shortest build I can find is 52 minutes, the longest being 1304. Yet the average time is 45 minutes.....

I'll restart the app tonight, then re-index - never got round to it before. Then check again and see if this changes, but I can't see why it would, Also, the rss allbuilds.xml and failedbuilds.xml don't include the beetlejuice builds, but may still contain the deleted builds that were marked as successful even though they weren't.

any obvious ideas why this would be the case? I can manually calculate it to see, but if the minimum successful build is 52 I don't see how it could drop an average of 45...



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Riaz Khanmohamed added a comment - 18/Oct/06 11:24 AM
As a follow-on, I did indeed delete all the successful builds I didn't want included, but it would seem that they still show up in the graphs, so I'm guessing they're still there and still being used for the average time. I'm guessing the delete build operation doesn't fully remove the existence of that build...

Mark Chaimungkalanont [Atlassian] added a comment - 18/Oct/06 07:03 PM
Riaz,

Thanks for that info.

The only thing I can think of immediately is that the build results may still be cached? Have you tried restarting the server?

In any case, we'll look further into it and sort it out for 0.6

Cheers

Mark C


Riaz Khanmohamed added a comment - 19/Oct/06 06:15 AM
Restarted last night, seems to be ok now. I think the 1308 hanged build that was successful may have had some influence in correcting the time, but at least it's closer to reality now. So yeah, I'm guessing it's probably a caching thing as you mentioned.

Mark Chaimungkalanont [Atlassian] added a comment - 01/Nov/06 09:24 PM
We've done some pretty big changes around this, it seems to work now

Riaz Khanmohamed added a comment - 02/Nov/06 02:47 AM
seems to have sorted itself out now after a restart, hasn't caused any problems since so you can close this one now if you want, thanks.