- Type:
- Bug
- Priority:
-
Normal
- State:
- Fixed
- Subsystem:
- Unknown
- Reporter:
- Gibson (rxgibson)
- Assignee:
- Olesya Smirnova (lesya)
- Affects:
- TeamCity 1.1
- Fixed in:
- 1.2 RC 1 (1771), TeamCity 1.2
- Created:
- 20 months ago (01 Dec 2006 21:02)
- Updated:
- 19 months ago (15 Jan 2007 16:11)
- Votes:
- 0
- Resolved:
- —
- JIRA source:
- TW-1279
- Build:
- 1730
There must be a long comment or something, but my builds all have the same error message with the same details - "column truncated"
Looking in the SVN history shows that the last commit has a comment with a length of 284 characters.
Issue wasresolved
-
Gibson (rxgibson)
20 months ago (01 Dec 2006 21:06)
Subsequent to this problem, builds that are supposed to trigger on VCS commit have to be launched manually.
-
Gibson (rxgibson)
20 months ago (04 Dec 2006 11:39)
Actually, nothing is getting checked out at all, the manually launched builds just build with 0 changes (so I suppose they're building from the revision before the server got "stuck")
-
Gibson (rxgibson)
20 months ago (04 Dec 2006 11:49)
Forgot to mention, I'm using MySQL as my underlying DB.
-
Gibson (rxgibson)
20 months ago (04 Dec 2006 12:34)
I worked around this by widening the relevant column, but it is TeamCity's responsibility to make sure data that is being written fits into the given column/table. I don't mind if that column is truncated (it's not TeamCity's responsibility to keep a complete version history, I have my Subversion server for that), but obviously it shouldn't crash in this case.
| Old | New | |
| Gibson (rxgibson) - 19 months ago (15 Jan 2007 16:11) | ||
Gibson (rxgibson)
20 months ago (01 Dec 2006 21:03)Relevant part of teamcity-vcs attached. It seems that the "500 Internal server error" isn't serious, but the "Data truncation" is ...