How that could be… All the tests are okay on my machine
Alexandre
> On Feb 26, 2016, at 4:03 PM, Christophe Demarey
> wrote:
>
> For this job, the image crashes because of an OutOfMemory as you can check
> here:
For this job, the image crashes because of an OutOfMemory as you can check
here: https://ci.inria.fr/moose/job/roassal2/2253/console
Le 26 févr. 2016 à 16:01, Christophe Demarey a écrit :
> Thanks for the link.
>
> The ugly java stack trace is because the junit result publisher jenkins
>
Thanks for the link.
The ugly java stack trace is because the junit result publisher jenkins plugin
tries to parse a file that is not well generated.
It happens when the image crashes during tests: the xml output does not contain
end tags.
As Aliaksei sait, probably dut to the cairo lib
Hi Chris,
for example
https://ci.inria.fr/moose/job/roassal2/2253/testReport/junit/Roassal2GT-Test/xml/_failed_to_read_/
On Fri, Feb 26, 2016 at 2:47 PM, Christophe Demarey <
christophe.dema...@inria.fr> wrote:
> Hi Alex,
>
> Could you provide the link to the job providing this output?
>
> Le
Hi!
We regularly get this error:
Failed to read test report file /builds/workspace/roassal2/Roassal2GT-Test.xml
org.dom4j.DocumentException: Error on line 27 of document
file:///builds/workspace/roassal2/Roassal2GT-Test.xml : XML document structures
must start and end within the same entity.