[pkg-php-pear] Bug#713780: php-mail: FTBFS: tests failed

[Lucas Nussbaum]

Source: php-mail
Version: 1.2.0-4
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> dh_link -O--buildsystem=phppear
> chmod +x ./debian/tests_run
> ./debian/tests_run Mail-1.2.0
> Testing with 13659.phpt
> PHPUnit 3.6.10 by Sebastian Bergmann.
> 
> .
> 
> Time: 1 second, Memory: 3.00Mb
> 
> OK (1 test, 1 assertion)
> Testing with 9137.phpt
> PHPUnit 3.6.10 by Sebastian Bergmann.
> 
> .
> 
> Time: 0 seconds, Memory: 3.00Mb
> 
> OK (1 test, 1 assertion)
> Testing with 9137_2.phpt
> PHPUnit 3.6.10 by Sebastian Bergmann.
> 
> .
> 
> Time: 0 seconds, Memory: 3.00Mb
> 
> OK (1 test, 1 assertion)
> Testing with rfc822.phpt
> PHPUnit 3.6.10 by Sebastian Bergmann.
> 
> .
> 
> Time: 0 seconds, Memory: 3.00Mb
> 
> OK (1 test, 1 assertion)
> Testing with smtp_error.phpt
> PHPUnit 3.6.10 by Sebastian Bergmann.
> 
> F
> 
> Time: 0 seconds, Memory: 3.25Mb
> 
> There was 1 failure:
> 
> 1) smtp_error.phpt
> --- Expected
> +++ Actual
> @@ @@
> -Failed to connect to bogus.host.tld:25 [SMTP: Failed to connect socket: fsockopen(): unable to connect to bogus.host.tld:25 (php_network_getaddresses: getaddrinfo failed: Name or service not known) (code: -1, response: )]
> +Failed to connect to bogus.host.tld:25 [SMTP: Failed to connect socket: php_network_getaddresses: getaddrinfo failed: Name or service not known (code: -1, response: )]
> 
> /usr/bin/phpunit:46
> 
> FAILURES!
> Tests: 1, Assertions: 1, Failures: 1.
> make[1]: *** [override_dh_link] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/06/20/php-mail_1.2.0-4_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.