Trying to track down cause behind some test failures in Groovy Build

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:
http://teamcity.jetbrains.com/viewLog.html?buildId=28369&tab=buildResultsDiv&buildTypeId=bt10

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?

Any thoughts?

Thanks, Paul.

6 comments
Comment actions Permalink

Paul, thank you for pointing that! It seems something is broken on our side, we'll will try find cause of these errors.

0
Comment actions Permalink

Thanks Pavel, let me know if there is anything I can do to assist.

0
Comment actions Permalink

I found the problem - it seems these tests configure Java security manager so that opening of the network sockets is prohibited. Sockets are required by TeamCity to send messages to the server. Since the sockets are not available agent won't be able to deliver test output to the server, but at least we can avoid stack overflow error. We will prepare a patch and install it on teamcity.jetbrains.com.

0
Comment actions Permalink

Cool, thanks. I'll be keen to try it out once you have the patch in place! Well done spotting the cause.

0
Comment actions Permalink

Please take a look, the patch is installed on teamcity.jetbrains.com.

0
Comment actions Permalink

Yes, excellent - that all seems to be working fine. Thanks!

0

Please sign in to leave a comment.