[Out of memory: GC overhead limit exceeded] seemingly coming from TeamCity

Hi,
just got this message in my full build log this morning.
It doesn't seem to affect the build, but this is what is reported in the main project page, letting people thing that the build is in error.

Is it a buildAgent memory setting that need to be increased?
This shouldn't be part of the Maven build right? So Maven memory settings cannot affect this part?

Publishing artifacts
[23:29:00]: [Publishing artifacts] Paths to publish: [/opt/local/buildAgent/temp/buildTmp/.tc-maven-bi/maven-build-info.xml.gz => .teamcity]
[23:29:00]: [Publishing artifacts] Sending files
[23:29:00]: [Out of memory: GC overhead limit exceeded] {build.status.text}
[23:29:00]: [Out of memory: GC overhead limit exceeded] {build.status.text}
[23:29:00]: Publishing artifacts (4s)
[23:29:00]: [Publishing artifacts] Paths to publish: [/opt/local/buildAgent/work/fbffa6120f5b9756/coverage.ic]
[23:29:00]: [Publishing artifacts] Sending files
[23:29:00]: Publishing artifacts (4s)
[23:29:00]: [Publishing artifacts] Paths to publish: [/opt/local/buildAgent/work/fbffa6120f5b9756/coverage.params]
[23:29:00]: [Publishing artifacts] Sending files
[23:29:00]: Generating coverage report... (8s)
[23:29:07]: [Generating coverage report...] Publishing artifacts (1s)
[23:29:07]: [Publishing artifacts] Paths to publish: [/opt/local/buildAgent/work/fbffa6120f5b9756/coverage.zip]
[23:29:07]: [Publishing artifacts] Sending files
[23:29:09]: Calculating coverage statistics...
[23:29:09]: [Calculating coverage statistics...] ##teamcity[buildStatisticValue key='CodeCoverageL' value='8.876149']
[23:29:09]: [Calculating coverage statistics...] ##teamcity[buildStatisticValue key='CodeCoverageAbsLCovered' value='7943.0']
[23:29:09]: [Calculating coverage statistics...] ##teamcity[buildStatisticValue key='CodeCoverageAbsLTotal' value='89487.0']
[23:29:09]: [Calculating coverage statistics...] ##teamcity[buildStatisticValue key='CodeCoverageM' value='15.059071']
[23:29:09]: [Calculating coverage statistics...] ##teamcity[buildStatisticValue key='CodeCoverageAbsMCovered' value='3021.0']
[23:29:09]: [Calculating coverage statistics...] ##teamcity[buildStatisticValue key='CodeCoverageAbsMTotal' value='20061.0']
[23:29:09]: [Calculating coverage statistics...] ##teamcity[buildStatisticValue key='CodeCoverageC' value='41.535557']
[23:29:09]: [Calculating coverage statistics...] ##teamcity[buildStatisticValue key='CodeCoverageAbsCCovered' value='660.0']
[23:29:09]: [Calculating coverage statistics...] ##teamcity[buildStatisticValue key='CodeCoverageAbsCTotal' value='1589.0']
[23:29:09]: Surefire report watcher
[23:29:09]: [Surefire report watcher] 4 file(s) found
[23:29:09]: Waiting for 2 service processes to complete
[23:29:09]: Publishing artifacts
[23:29:09]: [Publishing artifacts] Paths to publish: [teamcity-info.xml]
[23:29:09]: [Publishing artifacts] Sending files
[23:29:09]: Build finished

2 comments
Comment actions Permalink

Hi

Could you please show full build log, and teamcity-agent.log
From this cut I cannot tell for sure where this error comes from.

Thanks
Michael

0
Comment actions Permalink

Hi Michael,

I got it solved yesterday, it was a bad test that retrieving hundreds of thousands JPA entities.

It's just weird that the [Out of memory: GC overhead limit exceeded] was appearing so late in the build log, letting think that it was the TC `Publishing artifacts` section of the build that was causing the problem.

cheers

0

Please sign in to leave a comment.