On 29/06/17 20:25, Roger Leigh wrote:
On 29/06/17 20:17, Cantor, Scott wrote:
On 6/29/17, 3:02 PM, "Roger Leigh" <rle...@codelibre.net> wrote:

The recent trunk changes broke a few of the unit tests.

I don't understand how, other than the ones that are for some reason depending on the output of the parameter options for the DOMCount sample. That seems like an odd test, but it certainly would have broken.

Since nothing should be actually invoking the sample with the new option, I don't know why a new error would be raised in the tests, it defaults to behaving the same as before, allowing DTDs.

Do you need a hand looking at fixing any of these bits?

I don't know any of the tests or even how to run them, so probably.

If the tests can be run locally with an autotools build, I haven't found that trick yet.

It's "scripts/sanityTest.pl", a Perl script which runs all the tests, concatenates their output, and then diffs it with the expected output. It fails if the output differs or the tests fail prematurely.

Actually, just run "make check" which builds the tests and runs them for you.

---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: c-dev-h...@xerces.apache.org

Reply via email to