> >Dave, did you know this gold file namespace85.out checkin would
fail?
> >Everything else seems happy and passing.
> >- Shane
>Yes, I knew that. The problem has bug #3464 on it.
>Do I have to add namespace85 to some list in some props file?
>.................David Marston
Well, defacto we're managing the 'smoketest' target (either from
java/build.xml or test/build.xml) to report a pass for all tests
checked into conf/ with the default flavor. If you have a specific
test that you've changed, then report a bugzilla bug, and then edit
test.properties to exclude it from the smoketest (so developers won't
think this is a new problem that they caused with their recent
changes).
xml-xalan/test/test.properties
Edit/add to the below lines as needed; be sure to include a new comment
line tying the excluded test to the bugzilla entry!
# Bugzilla2548 attribset42.xsl;attribset43.xsl
# Bugzilla1133 lre10.xsl;lre21.xsl
# Bugzilla-new-number testname.xsl
smoketest.conf.excludes=attribset42.xsl;attribset43.xsl;lre10.xsl;lre21.xsl;testname.xsl
Obviously, this policy is subject to amendment by the community, but I
think it's good enough for now. In a much more structured development
environment, I'd take the hard-line QE approach and always run these
tests, but that's a bit difficult to manage here.
Hey, how many of our committers and patch-sender-in-ers do run 'build
smoketest' and ensure it passes before checking in, like you should?
Any suggestions for improvement welcome.
- Shane
=====
<eof aka="mailto:[EMAIL PROTECTED]";
quote="Odo: [You'd shoot a man in the back?]
Garak: [Well, it's the safest way, isn't it?]"/>
__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger
http://im.yahoo.com
