Randy Kobes wrote:

On Fri, 19 Sep 2003, Steve Hay wrote:



Stas Bekman wrote:



Steve Hay wrote:



I have found this, though:

Recall that running just the "filter" tests (as "perl t/TEST
t/filter") makes it work (except for the in_str_consume test that
sadly still fails).

Well, running "perl t/TEST t/api t/filter" also succeeds, as does
"perl t/TEST t/apr t/filter" (except for apr/perlio, of course), but
"perl t/TEST t/api t/apr t/filter" makes the first filter test --
both_str_con_add.t -- crash Apache.



I think the relevant test here is api/rflush.t - skipping
it, and running all other api/ and apr/ tests, allows the
filter tests to run and, except for the occasional failure
of in_str_consume, all pass.


Homing in further:

- perl t/TEST t/api t/apr t/filter/both_str_con_add
causes filter/both_str_con_add to fail

- the same, but skipping api/rflush
allows filter/both_str_con_add to succeed

- perl t/TEST t/api/rflush t/apr t/filter/both_str_con_add
*doesn't* cause filter/both_str_con_add to fail again!

- perl t/TEST t/api/lookup_uri t/api/rflush t/apr t/filter/both_str_con_add
does now cause filter/both_str_con_add to fail again.

So it is a combination of api/lookup_uri+api/rflush (with apr) that breaks filter/both_str_con_add. Skipping either one of those two api/ tests allows filter/both_str_con_add to succeed.

- Steve


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to