- Type:
- Bug
- Priority:
-
Critical
- State:
- Fixed
- Subsystem:
- Server Web
- Reporter:
- Yegor Yarko (yaegor)
- Assignee:
- Sergey Anchipolevsky (serganch)
- Affects:
- No affected versions
- Fixed in:
- TeamCity 3.1 (6760)
- Created:
- 12 months ago (06 Nov 2007 10:15)
- Updated:
- 9 months ago (21 Feb 2008 13:20)
- Votes:
- 0
- Resolved:
- —
- JIRA source:
- TW-3749
Issue has no links
see attached screenshot.
If a build is delayed, the one assigned to the same agent should probably be delayed too
Issue wasresolved
| Old | New | |
| Yegor Yarko (yaegor) - 9 months ago (21 Feb 2008 13:20) | ||
| Fixed in version | Benares Minor (3.1) | |
| Fixed in version | TeamCity 3.1 (6760) | |
Sergey Anchipolevsky (serganch)
11 months ago (23 Nov 2007 15:04)1. I don't agree this is critical
2. "Delayed" means the expected time to start is 0 ("The build should start shortly"). This is not true for the subsequent build. Generally we aren't deceiving the user bacause if the first build start right now (which is quite possible) this time is pretty what we're expecting.
3. I think we should approach to this problem from the other direction -- reduce the probability of appearing "delayed" builds in the queue
Yegor Yarko (yaegor)
11 months ago (27 Nov 2007 13:15)Can use some special notation for such builds. e.g. "2h:46m+?" with the appropriate description that build takes longer then estimated on the agent planned for this build