Re: FW: [GUMP] Test Failure
Mark, One possibility is to have log4j tests output both the witness file and the tested file upon failure by modifying Compare.compare() method. Thus, instead of [junit] Files [output/plugins.PluginTestCase.test1.txt] and [witness/plugins.PluginTestCase.test1.txt] differ on line 65 [junit] One reads: [DEBUG - plugin plugin1-id1 shutdown]. [junit] Other reads:[DEBUG - plugin plugin2-id4 shutdown]. [junit] - --- we would see [junit] Files [output/plugins.PluginTestCase.test1.txt] and [witness/plugins.PluginTestCase.test1.txt] differ on line 65 [junit] One reads: [DEBUG - plugin plugin1-id1 shutdown]. [junit] Other reads:[DEBUG - plugin plugin2-id4 shutdown]. [junit] - --- [junit] Dumping [output/plugins.PluginTestCase.test1.txt] [junit] - --- [junit] Dumping [witness/plugins.PluginTestCase.test1.txt] The advantage is that you do not the intervention of gump developers to send you the witness file or the tested file. As for the reasons for the failure, my hunch is that Sam machine orders the plugins differently. It might be simply because his JDK implements HaspMap differently or because it orders threads differently. Since I do not see multiple threads in the test case, it can only be the former possibility. Let us take continue this on log4j-dev. Hi Sam, I'll look at the dependencies, but it is not obvious how a difference there would affect this particular test. Is there any way that I can access the generated test output files to see if there is a clue there? -Mark -- Ceki -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: FW: [GUMP] Test Failure
[EMAIL PROTECTED] wrote: I am investigating the current failure with log4j during the nightly gump builds. Ceki said that I should post to this group, so I hope this is the right place. This is the right place. I am able to build log4j and run the log4j test without problems on my machine. So, I am confused about the failure in gump. How can I proceed with investigating this further? Is the source code and test files being used available somewhere on the web so I can take a look at them? I'm wondering if they are out-of-sync in some way. All sources are from cvs. The key difference is that generally the latest version (built from cvs) of every dependency is used. For convenience, there a copy of each is available at http://gump.covalent.net/jars/. The way the build actually operates is that the various jars (in this case, ant's, xerces, jms, junit, and javamail) are defined in the CLASSPATH, and then the following command is issued (adjust the paths as necessary) java -Xbootclasspath/p:/home/rubys/jakarta/ml-xerces2/java/build/xercesImpl.jar:/home/rubys/jakarta/xml-xerces2/java/build/xmlParserAPIs.jar org.apache.tools.ant.Main -Dbuild.sysclasspath=only -Dversion 20021217 thanks! -Mark - Sam Ruby -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: FW: [GUMP] Test Failure
Hi Sam, I'll look at the dependencies, but it is not obvious how a difference there would affect this particular test. Is there any way that I can access the generated test output files to see if there is a clue there? -Mark -Original Message- From: news [mailto:[EMAIL PROTECTED]]On Behalf Of Sam Ruby Sent: Tuesday, December 17, 2002 3:07 AM To: [EMAIL PROTECTED] Subject: Re: FW: [GUMP] Test Failure [EMAIL PROTECTED] wrote: I am investigating the current failure with log4j during the nightly gump builds. Ceki said that I should post to this group, so I hope this is the right place. This is the right place. I am able to build log4j and run the log4j test without problems on my machine. So, I am confused about the failure in gump. How can I proceed with investigating this further? Is the source code and test files being used available somewhere on the web so I can take a look at them? I'm wondering if they are out-of-sync in some way. All sources are from cvs. The key difference is that generally the latest version (built from cvs) of every dependency is used. For convenience, there a copy of each is available at http://gump.covalent.net/jars/. The way the build actually operates is that the various jars (in this case, ant's, xerces, jms, junit, and javamail) are defined in the CLASSPATH, and then the following command is issued (adjust the paths as necessary) java -Xbootclasspath/p:/home/rubys/jakarta/ml-xerces2/java/build/xerces Impl.jar:/home/rubys/jakarta/xml-xerces2/java/build/xmlParserAPIs.jar org.apache.tools.ant.Main -Dbuild.sysclasspath=only -Dversion 20021217 thanks! -Mark - Sam Ruby -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
