This is really weird, now I'm getting a new error. It appears to be coming from one of the tests that I committed yesterday. It's causing Tomcat to choke and spit out a 500 server error.
I'm already looking into it, but I won't be able to commit the patch. My work connection doesn't allow ports other than http and ftp, and at home my DSL provider (Telocity) is in the middle of a switch to a new provider (and I don't even have the modem yet....crap). I'll send in a patch soon. -- James Mitchell ----- Original Message ----- From: "Robert Leland" <[EMAIL PROTECTED]> To: "Struts Developers List" <[EMAIL PROTECTED]> Sent: Friday, February 07, 2003 11:13 AM Subject: Re: Cactus Test Failures? > Craig R. McClanahan wrote: > > Trying to run the "test.tomcat.40" and "test.tomcat.41" targets, I get a > > JUnit failure on the "testInitDestroyInternal" testcase. The logged > > message implies that this is because Tomcat is returning a 404 error for > > "/test/ServletRedirector". > > > > Did something change in this test recently? Or maybe I need a different > > version of Cactus (1.4) or JUnit (3.8.1)? > > We'll need to update the unit tests to use cactus 1.4, I forgot what > the change was but version 1.3 had both the new and old classes and > provided a transition point. I made a comment in a Bugzilla > message about that back in November or so. > > -Rob > > > --------------------------------------------------------------------- > 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]