-
Notifications
You must be signed in to change notification settings - Fork 51
Open
Description
Today I tested WWW-Mechanize as part of the CPAN-River-3000 against perl-5.31.3. The test named in the subject line hung indefinitely:
{
author => "OALDERS",
dist => "WWW-Mechanize",
distname => "WWW-Mechanize-1.91",
distversion => 1.91,
grade => "FAIL",
prereqs => undef,
test_output => [
"Building and testing WWW-Mechanize-1.91",
"cp lib/WWW/Mechanize/Link.pm blib/lib/WWW/Mechanize/Link.pm",
"cp lib/WWW/Mechanize/FAQ.pod blib/lib/WWW/Mechanize/FAQ.pod",
"cp lib/WWW/Mechanize/Image.pm blib/lib/WWW/Mechanize/Image.pm",
"cp lib/WWW/Mechanize.pm blib/lib/WWW/Mechanize.pm",
"cp lib/WWW/Mechanize/Cookbook.pod blib/lib/WWW/Mechanize/Cookbook.pod",
"cp lib/WWW/Mechanize/Examples.pod blib/lib/WWW/Mechanize/Examples.pod",
"cp bin/mech-dump blib/script/mech-dump",
...
"t/local/post.t ........................... ok",
"Error GETing http://127.0.0.1:17036/: Can't connect to 127.0.0.1:17036 (Connection refused) at t/local/referer.t line 39.",
"-> FAIL Timed out (> 1800s). Use --verbose to retry.",
],
via => "App::cpanminus::reporter 0.17 (1.7044)",
}
This 30-minute hang caused (a) caused the overall test harness to take 30 minutes longer to complete than would be expected; (b) caused WWW-Mechanize to be graded FAIL
, which in turn meant that all of this distros reverse dependencies could not be reached during automated testing.
Could this test be revised so that it is not run during automated testing? Or could the test be made more robust otherwise?
Thank you very much.
Jim Keenan