https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8227
--- Comment #4 from Sidney Markowitz <sidney@sidney.com> ---
(In reply to Giovanni Bechis from comment #2)
> The bits added to DependencyInfo.pm breaks install on some networks where
> SpamAssassin would work by adding "dns_server 127.0.0.1" option.
What I was trying to do was overkill anyway. Instead killing the entire build,
and not even suppressing all network tests, since most of them won't trigger
big DNS replies or whatever is going wrong with multihomed addresses, I can do
this:
Put the test of getting the txttcp large packet in a function in t/SATest.pm
and have only the tests that actually fail when it is a problem call it (not
all network tests have to care about it). If it fails, they can skip all tests
with a warning message that dns_server may have to be set when running
SpamAssassin on that system.
Add the check of multihomed to t/spamc_H.t so it can skip the tests with a
similar warning if something is wrong with the local DNS resolver that affects
getting those records.
That will prevent the egregious failure reports on those CPAN test machines
that have bad DNS configuration without breaking any builds, and will warn
people who need to use dns_server options in their configuration.
How does that seem?
--
You are receiving this mail because:
You are the assignee for the bug.
--- Comment #4 from Sidney Markowitz <sidney@sidney.com> ---
(In reply to Giovanni Bechis from comment #2)
> The bits added to DependencyInfo.pm breaks install on some networks where
> SpamAssassin would work by adding "dns_server 127.0.0.1" option.
What I was trying to do was overkill anyway. Instead killing the entire build,
and not even suppressing all network tests, since most of them won't trigger
big DNS replies or whatever is going wrong with multihomed addresses, I can do
this:
Put the test of getting the txttcp large packet in a function in t/SATest.pm
and have only the tests that actually fail when it is a problem call it (not
all network tests have to care about it). If it fails, they can skip all tests
with a warning message that dns_server may have to be set when running
SpamAssassin on that system.
Add the check of multihomed to t/spamc_H.t so it can skip the tests with a
similar warning if something is wrong with the local DNS resolver that affects
getting those records.
That will prevent the egregious failure reports on those CPAN test machines
that have bad DNS configuration without breaking any builds, and will warn
people who need to use dns_server options in their configuration.
How does that seem?
--
You are receiving this mail because:
You are the assignee for the bug.