I'm sure the bsh error is because I don't have that jar. I was mostly worried about the websampler issue - that may also be due to me missing a jar though. I don't even know what jar I need for that. -Mike
On Wed, 2005-08-17 at 20:01 +0100, sebb wrote: > Forgot to add that the JMX failures are probably benign - I think they > are CRLF vs LF problems (must get around to fixing the compare). > > I can fix the HTTP link error - I thought it was benign, but the Help > does not scroll to the correct place for that sampler. > > I've already created the tag, but that can be moved for the > (hopefully) few files that need fixing... > > S. > On 17/08/05, sebb <[EMAIL PROTECTED]> wrote: > > On 17/08/05, Michael Stover <[EMAIL PROTECTED]> wrote: > > > Here's what I get: > > > > > > 1) testLoadAndSave > > > (org.apache.jmeter.save.TestSaveService)com.thoughtworks.xstream.converters.ConversionException: > > > WebServiceSampler : WebServiceSampler > > > [java] ---- Debugging information ---- > > > [java] required-type : > > > org.apache.jorphan.collections.ListedHashTree > > > [java] cause-message : WebServiceSampler : WebServiceSampler > > > [java] class : org.apache.jmeter.save.ScriptWrapper > > > [java] message : WebServiceSampler : WebServiceSampler > > > [java] line number : 929 > > > [java] > > > path : /jmeterTestPlan/hashTree/hashTree/hashTree > > > [4]/hashTree[5]/WebServiceSampler > > > [java] cause-exception : > > [...] > > > > [java] FAILURES!!! > > > [java] Tests run: 933, Failures: 3, Errors: 1 > > > > > > > I don't get that failure... > > > > [java] There were 2 failures: > > [java] 1) > > runGUITitle(org.apache.jmeter.junit.JMeterTest)junit.framework.As > > sertionFailedError: component_reference.xml needs 'HTTP Request HTTPCLient' > > anch > > or for org.apache.jmeter.protocol.http.control.gui.HttpTestSampleGui2 > > [java] at > > org.apache.jmeter.junit.JMeterTest.runGUITitle(JMeterTest.jav > > a:350) > > [java] at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown > > Source) > > [java] at > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet > > hodAccessorImpl.java:25) > > [java] at org.apache.jorphan.test.AllTests.main(AllTests.java:197) > > [java] 2) > > testLoadAndSave(org.apache.jmeter.save.TestSaveService)junit.fram > > ework.AssertionFailedError: One or more failures detected > > [java] at > > org.apache.jmeter.save.TestSaveService.testLoadAndSave(TestSa > > veService.java:92) > > [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native > > Method) > > [java] at > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces > > sorImpl.java:39) > > [java] at > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet > > hodAccessorImpl.java:25) > > [java] at org.apache.jorphan.test.AllTests.main(AllTests.java:197) > > > > [java] FAILURES!!! > > [java] Tests run: 993, Failures: 2, Errors: 0 > > > > [java] +++++++++++ > > [java] ------------ > > > > I suspect the extra 60 tests I'm running may indicate a different > > setup - what optional jars have you got (e.g. in lib/opt)? > > > > > > S. > > > > > On Wed, 2005-08-17 at 14:23 -0400, Peter Lin wrote: > > > > > > > which tests are failing 2.1? > > > > > > > > peter > > > > > > > > > > > > On 8/17/05, Michael Stover <[EMAIL PROTECTED]> wrote: > > > > > Actually, there are some failing unit tests that should be addressed > > > > > before a real release. Are we talking a release candidate or actual > > > > > release? > > > > > > > > > Actual release. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
