Not sure this belongs here but seemed worth asking a question before raising an issue.
I am trying to track down the causes for some test failures here:
The problems don't seem to be related to changes in the Groovy code base. The tests run fine locally and on several other build servers. There are five tests failing. The dates when they started failing looks suspiciously close to when TeamCity 5 came out.
The stacktraces seem to show an infinite loop in teamcity code? My current hunches include:
* TeamCity 5 requires more memory and pushed these tests over the edge of some threshold. Is there some scope for changing memory settings?
* Bug in TeamCity stacktrace printing code?
* Bug in Groovy, e.g. some infinitely recursive data structure that TeamCity is trying to print out, e.g. exception pointing to itself as cause - that is somehow being ignored in other environments?