• Type: Bug
• Resolution: Fixed
• Priority: Medium
• Fix Version/s: 2.6 rc1, 2.6
• Affects Version/s: 2.6 rc1
• Component/s: None
• Labels:

  None
• Environment:

  tardigrade

[BAM-5812] Current Activity -> Queue does not show all queued builds

Collapse comment: MarkC added a comment - 18/May/2010 1:48 AM

MarkC added a comment - 18/May/2010 1:48 AM

Mate looking at the time lines of this, I don't think it's a bug, it might be late night at work timing issue.

First screenshot is possibly from:

2010-05-18 04:10:50,286 INFO [http-8085-5] [AccessLogFilter] mwent http://tardigrade.sydney.atlassian.com:8085/bamboo/build/viewBuildSummary!default.action?buildKey=BAM-RESTFUNC 42594kb

where both 4227 & 4228 are queued & 4228 started @ 4:14 on an EC2 agent until:

2010-05-18 04:15:27,665 INFO [http-8085-4] [AccessLogFilter] mwent http://tardigrade.sydney.atlassian.com:8085/bamboo/admin/elastic/shutdownElasticInstance.action 54087kb

and so the 4228 build was lost (expected behaviour), then you checked out the 2nd screenshot at possibly:

2010-05-18 04:16:03,685 INFO [http-8085-8] [AccessLogFilter] mwent http://tardigrade.sydney.atlassian.com:8085/bamboo/start.action?selectedTab=currentTab 34088kb

where 4227 is happily building on Panda and 4228 has gone offline (the error down the bottom) and both has gone out of the queue. I can definitely see how it could be a bit confusing but all seems to be working okay in this instance.

Expand comment: MarkC added a comment - 18/May/2010 1:48 AM

MarkC added a comment - 18/May/2010 1:48 AM Mate looking at the time lines of this, I don't think it's a bug, it might be late night at work timing issue. First screenshot is possibly from: 2010-05-18 04:10:50,286 INFO [http-8085-5] [AccessLogFilter] mwent http://tardigrade.sydney.atlassian.com:8085/bamboo/build/viewBuildSummary!default.action?buildKey=BAM-RESTFUNC 42594kb where both 4227 & 4228 are queued & 4228 started @ 4:14 on an EC2 agent until: 2010-05-18 04:15:27,665 INFO [http-8085-4] [AccessLogFilter] mwent http://tardigrade.sydney.atlassian.com:8085/bamboo/admin/elastic/shutdownElasticInstance.action 54087kb and so the 4228 build was lost (expected behaviour), then you checked out the 2nd screenshot at possibly: 2010-05-18 04:16:03,685 INFO [http-8085-8] [AccessLogFilter] mwent http://tardigrade.sydney.atlassian.com:8085/bamboo/start.action?selectedTab=currentTab 34088kb where 4227 is happily building on Panda and 4228 has gone offline (the error down the bottom) and both has gone out of the queue. I can definitely see how it could be a bit confusing but all seems to be working okay in this instance.