i just committed some verbose messages, so if you cvs up, then t/TEST -v t/modules/access.t you will see the config and what is expected for each test case. -j
On Fri, Aug 24, 2001 at 02:03:39PM -0400, Cliff Woolley wrote: + + I'm getting failures in the mod_access tests: + + Failed Test Status Wstat Total Fail Failed List of failed + ------------------------------------------------------------------------------- + modules/access. 408 31 7.60% 4, 20-21, 24, 26, 28, 30, 38, 55, + 72, 89, 106-107, 123-124, 141, + 154, 168, 170, 175, 192, 209, + 226, 277, 290, 304, 306, 311, + 328, 345, 362 + + These have always failed for me, though Doug tells me they work for him. + It's probably a configuration issue somehow. Any ideas? I do have an + entry for localhost in my /etc/hosts file, btw. + + + On Fri, 24 Aug 2001, Doug MacEachern wrote: + + > hmm, well if you run 't/TEST -d lwp t/modules/access' + > you'll get some tracing of the request uri and response headers. + + One of them looks like this: + + GET http://localhost:8529/modules/access/htaccess/index.html : + HTTP/1.1 200 OK + Connection: close + Date: Fri, 24 Aug 2001 17:50:11 GMT + Accept-Ranges: bytes + Server: Apache/2.0.25-dev (Unix) DAV/2 + Content-Length: 0 + Content-Type: text/html + ETag: "3a4733-0-8cd1d080" + Last-Modified: Mon, 06 Aug 2001 18:19:30 GMT + Client-Date: Fri, 24 Aug 2001 17:50:11 GMT + Client-Peer: 127.0.0.1:8529 + X-Content-Length-Note: added by Apache::TestReqest + + not ok 362 + + > anything useful in the error_log ? + + It's really hard to distinguish the "good" errors from the "bad" errors, + especially since you can't run just a single test number... + + > might be worth posting to the test-dev list, john sachs who wrote the test + > might have some ideas. + + Here goes... + + Thanks, + Cliff + + + -------------------------------------------------------------- + Cliff Woolley + [EMAIL PROTECTED] + Charlottesville, VA + +
