Failure is:

FATAL: Unkown internal error. Please, open an issue in Jenkins JIRA with the complete stack trace. If possible, try including the JUnit XML(s) too.
hudson.plugins.testlink.result.TestResultSeekerException: Unkown internal error. Please, open an issue in Jenkins JIRA with the complete stack trace. If possible, try including the JUnit XML(s) too.
at hudson.plugins.testlink.result.junit.JUnitTestCasesTestResultSeeker.seek(JUnitTestCasesTestResultSeeker.java:117)
at hudson.plugins.testlink.result.TestResultsCallable.seekTestResults(TestResultsCallable.java:111)
at hudson.plugins.testlink.result.TestResultsCallable.invoke(TestResultsCallable.java:153)
at hudson.plugins.testlink.result.TestResultsCallable.invoke(TestResultsCallable.java:47)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:1994)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:287)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:636)
Caused by: java.lang.OutOfMemoryError: Java heap space
ERROR: An error occured while trying to retrieve the test results: Unkown internal error. Please, open an issue in Jenkins JIRA with the complete stack trace. If possible, try including the JUnit XML(s) too..

We recently started using the testlink plugin. I was evaluating it until last night when I applied it to our 'real' build system.

The job that failed above had succeeded before. I also saw this fail with OutOfMemoryError when using this pattern for the JUnit XML files: **/TEST*Test.xml .

Changing the pattern to **/Test*TestSuites.xml seemed to get us over the failure, but apparently not.

I have attached the JUnit XML files.

After seeing suggestions for increasing the max memory for slaves when an OutOfMemory error occurs I set the slave memory setting to -Xmx1024m.