-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Centos 6.4
A few days ago one of my FitNesse test builds started producing corrupt XML logs, such that at the conclusion of the first result element the entire file to that point repeated itself, starting with the initial <?xml element, following which no more output was produced (see attachment).
This of course resulted in the Jenkins build failing, because the XML file was corrupt.
My other FitNesse test builds are continuing to perform normally. I've made changes to FitNesse recently, but not the Jenkins build configuration. The tests continue to run fine when run as a suite from the FitNesse web interface.