Xerces-C 3.1.2 beta-2 available, call for testing

[Cantor, Scott]

I've uploaded a second beta of Xerces-C 3.1.2 [2] containing a couple of
small fixes (VS2012 solution file fix, a backport of an XMLString
binToText bug reported yesterday) and a tweak to the automake settings so
I can generate a ZIP distribution from make dist.

Just want to keep the test sources current.

Thank you to everybody who's smoke tested.

I have tried to run a few of the programs in test/ and they mostly did ok
but one actually crashed (the DOM Normalizer test). I then reproduced the
exact same exception crash using the 3.1.1 sources, so this isn't a
regression, it was already behaving that way. I'm guessing the tests are
out of date in some cases, but I don't know them well enough to look at it.

-- Scott


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

[Gareth Reakes]

On OSX compiles fine but test run produces this attached failure diff.

G

[Cantor, Scott]

Post by Gareth Reakes
On OSX compiles fine but test run produces this attached failure diff.

Compared to 3.1.1 you mean?

How do the tests get run as a unit? Do you know which test is giving that
different result?

-- Scott


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

[Gareth Reakes]

Post by Cantor, Scott

Post by Gareth Reakes
On OSX compiles fine but test run produces this attached failure diff.

Compared to 3.1.1 you mean?

No, compared to the committed test output file - scripts/sanityTest_ExpectedResult.log

Post by Cantor, Scott
How do the tests get run as a unit?

make check

Post by Cantor, Scott
Do you know which test is giving that
different result?

# Run SAXPrint. This tests long element names.
print ("\nTest of a long element name.\n");
system ("SAXPrint -v=never long.xml");
print ("\n\n");


G

[Cantor, Scott]

Post by Gareth Reakes
No, compared to the committed test output file -
scripts/sanityTest_ExpectedResult.log

Ok, I'll look at when that was committed.

Post by Gareth Reakes
make check

So it runs them as part of the test build? Ok, I didn't notice that, will
review that.

-- Scott


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

[Cantor, Scott]

Post by Gareth Reakes
On OSX compiles fine but test run produces this attached failure diff.

Somewhat surprisingly, on my OS X laptop, my test run has identical output
to what's checked in, no diff. But I did that out of subversion, not the
tarball, so I'll rerun the check with the tarball.

-- Scott


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

[Gareth Reakes]

Post by Cantor, Scott

Post by Gareth Reakes
On OSX compiles fine but test run produces this attached failure diff.

Somewhat surprisingly, on my OS X laptop, my test run has identical output
to what's checked in, no diff. But I did that out of subversion, not the
tarball, so I'll rerun the check with the tarball.

Do you have the file in your checkout?

/xerces-c-3.1.2/samples/data/long.xml

G



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

[Cantor, Scott]

Post by Gareth Reakes
Do you have the file in your checkout?
/xerces-c-3.1.2/samples/data/long.xml

No, it's not in the dist target, so that's the problem. I'll add it and
republish a third beta today.

One of the things I'm trying to clean up is the dist. It was quite
incomplete, which is a bad thing in general, it's important that it
include everything needed for every platform.

I left the tools that rebuild the web site out for the moment, because
those are pretty large, and the site inside the tree appears to be stale
anyway, but everything else I'm trying to include.

-- Scott

Т���������������������������������������������������������������������ХF�V�7V'67&�&R�R���â2�FWb�V�7V'67&�&T�W&6W2�6�R��&pФf�"FF�F����6����G2�R

[Cantor, Scott]

In case it matters, this is what I'm using with configure:

configure: Report:
configure: File Manager: POSIX
configure: Mutex Manager: POSIX
configure: Transcoder: icu
configure: NetAccessor: socket
configure: Message Loader: inmemory


Any of those different in your build that's giving different output?

-- Scott


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

[Gareth Reakes]

Post by Cantor, Scott
configure: File Manager: POSIX
configure: Mutex Manager: POSIX
configure: Transcoder: icu
configure: NetAccessor: socket
configure: Message Loader: inmemory

Yes, they are different. I did ./configure with no options.

configure: Report:
configure: File Manager: POSIX
configure: Mutex Manager: POSIX
configure: Transcoder: macosunicodeconverter
configure: NetAccessor: curl
configure: Message Loader: inmemory

F