Boost-build run rule outputs unparseable XML with Boost.Test

[afoglia@…]

I'm trying to use boost-build's run rule to run tests built with Boost.Test and then have my continuous integration system parse the resulting XML to report on the tests. The problem is the output files generated by boost-build are no longer proper XML.

The problem is boost-build adds an extra line "EXIT STATUS: 0" (or whatever the status was). That makes the XML invalid, and XML parsers will throw an error.

The sensible solution is to not append the exit status to the captured output, but to put it in another file instead. Perhaps <basename>.exitcode or similar.

[Vladimir Prus]

I am afraid that this solution, while it will make your scripting solution happy, has the potential to break any other existing scripting solutions that expect the error status to be present in output file. Therefore, I am not planning to change this.