Skip Menu |
 

This queue is for tickets about the Net-SMTP-Verify CPAN distribution.

Report information
The Basics
Id: 125600
Status: open
Priority: 0/
Queue: Net-SMTP-Verify

People
Owner: BENNING [...] cpan.org
Requestors: SREZIC [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: 1.03
Fixed in: (no value)



Subject: Random test failures
Download (untitled) / with headers
text/plain 104b
See subject. An overview of fail/pass reports: http://matrix.cpantesters.org/?dist=Net-SMTP-Verify+1.03
Download (untitled) / with headers
text/plain 169b
Most of the random failures should be a result of missing internet connectivity in tests. In version 1.04 the remote tests are only run if ENV{INTERNET_TESTING} is set.
Download (untitled) / with headers
text/plain 764b
On 2018-10-10 12:32:51, BENNING wrote: Show quoted text
> Most of the random failures should be a result of missing internet > connectivity in tests.
I very much doubt this is the case. At least my smoker systems have a very stable internet connection, and many other CPAN distributions also depend on a working internet in their test suite, but don't show up any problems here. See for example http://www.cpantesters.org/cpan/report/e921a56a-c7a6-11e8-9e60-8631d1e3f978 : obviously resolv.t had a working internet connection, and it's unlikely that the following smtp.t did not. And there are may fails like this. Or do you think the internet connection on the remote side is problematic? Show quoted text
> > In version 1.04 the remote tests are only run if ENV{INTERNET_TESTING} > is set.
Download (untitled) / with headers
text/plain 1.7k
On 2018-10-10 12:32:51, BENNING wrote: Show quoted text
> Most of the random failures should be a result of missing internet > connectivity in tests. > > In version 1.04 the remote tests are only run if ENV{INTERNET_TESTING} > is set.
I have to re-open this ticket. 1.04 also shows random test failures (in smtp.t). I am not aware to set or unset INTERNET_TESTING on my smokers. A sample failure: # connecting to 127.0.0.1 on port 53474... # sending MAIL goodsender@gooddomain.tld... # server said: sender goodsender@gooddomain.tld OK # sending RCPT rcpt1@gooddomain.tld... # server said: recipient rcpt1@gooddomain.tld OK # sending RCPT rcpt2@gooddomain.tld... # server said: recipient rcpt2@gooddomain.tld OK # sending RCPT rcpt3@gooddomain.tld... # server said: recipient rcpt3@gooddomain.tld OK # sending QUIT... # connecting to 127.0.0.1 on port 50783... # sending pipelined bulk... # server response to MAIL: sender goodsender@gooddomain.tld OK # server response to RCPT rcpt1@gooddomain.tld: recipient rcpt1@gooddomain.tld OK # server response to RCPT rcpt2@gooddomain.tld: recipient rcpt2@gooddomain.tld OK # server response to RCPT rcpt3@gooddomain.tld: recipient rcpt3@gooddomain.tld OK # sending QUIT... # connecting to 127.0.0.1 on port 50783... # sending pipelined bulk... # server response to MAIL: badsender@gooddomain.tld Recipient address rejected: bad user # sending QUIT... # connecting to 127.0.0.1 on port 50783... # connection failed: Net::SMTP: 421 [Net::SMTP] Timeout # Failed test '2 rcpts must be successfull' # at t/smtp.t line 54. # got: '0' # expected: '2' # Failed test '1 rcpts must be permanent error' # at t/smtp.t line 55. # got: '0' # expected: '1' # Looks like you failed 2 tests of 19. t/smtp.t ............... Dubious, test returned 2 (wstat 512, 0x200) Failed 2/19 subtests
Download (untitled) / with headers
text/plain 129b
You're absolutly right. Has nothing todo with network issues. Seems like there are random errors with the SMTP mock test server.


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.