Marshall Galbraith

That's annoying that you have to deal with compiler bugs. I am actually trying to use the --xml argument, but I noticed none of the arguments worked. Here are the...

So I was looking at section "4.3.2 Command Line Options" in the pFUnit3-ReferenceManual.pdf assuming that things had not changed too much from version 3 to 4. There is a "-v"...

So I still can't specify an xml file with this change, and I still get a segfault when I provide a command that is not available. ``` cooltest --xml test.xml...

I blew away the "extern" directory in my build directory, and that seems to have fixed the xml ``` ./cooltest --xml 3 e3_Tt3 0.13432114E-03 e3_Tt3 0.66721437E-04 e3_Tt3 0.33991869E-04 0.13432114E-03 0.66721437E-04...

I'm also noticing that the xml output is only dumped to the screen. Would it be possible to have it duped to a file?

That is very strange... Let me try a fresh clone as well. Would it not be better to error out gracefully if someone does provide an unknown option? I prefer...

Yeah the fresh clone does not segfault with a bad input. Some dependency must not be quite right in the cmake files... Very strange... CMake is supposed to be good...

One last thing, what report format is the xml files? I'm using "Publish xUnit test result report" in Jenkins, and there are a large number of report format to choose...

I don't have a specific report format in mind. Which ever one that is easiest to implement that the Jenkins "Publish xUnit test result report" plugin can read would be...

Just wanted to ping you to see if you made any progress on the xml reporting of if you needed some help from me with it?