| Key: |
QB-836
|
| Type: |
Bug
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Blocker
|
| Assignee: |
Unassigned
|
| Reporter: |
AlSt
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 24/Feb/11 08:03 PM
Updated: 01/Mar/11 06:37 AM
|
|
| Component/s: |
None
|
| Affects Version/s: |
3.1.21
|
| Fix Version/s: |
3.1.22
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
File Attachments:
|
None
|
|
Image Attachments:
|
|
|
|
After migrating to QB 3.1 we have problems with exceeded queue sizes.
While the new handling of dependent builds is a huge improvement for us, now "regular" builds do not respect the number of workers in some cases.
I suspect that there is a correlation with schedule handling because of the almost concurrent dates (see screen shot).
|
|
Description
|
After migrating to QB 3.1 we have problems with exceeded queue sizes.
While the new handling of dependent builds is a huge improvement for us, now "regular" builds do not respect the number of workers in some cases.
I suspect that there is a correlation with schedule handling because of the almost concurrent dates (see screen shot).
|
Show » |
|
Scheduled builds do not respect queue size
Does these running builds depend on each other, in the form of one build triggering another build, or checking out artifacts from another build. In this case QB will consider them as a single build. This is reasonable from resource usage perspective, as waiting builds are not using any resources although their status is RUNNING.
Regards
Robin