Bug#713378: get-flash-videos: FTBFS: dh_auto_test: make -j1 test returned exit code 2

[Lucas Nussbaum]

Source: get-flash-videos
Version: 1.25~git2012.06.27-1
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»'
> PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t
> t/00_load.t .............. ok
> There is no form with the requested fields at /«PKGBUILDDIR»/blib/lib/FlashVideo/Site/Googlevideosearch.pm line 18
> There is no form with the requested fields at /usr/share/perl5/WWW/Mechanize.pm line 1897.
> # Looks like your test exited with 255 before it could output anything.
> t/google_video_search.t .. 
> Dubious, test returned 255 (wstat 65280, 0xff00)
> Failed 2/2 subtests 
> t/json.t ................. ok
> t/prefs.t ................ ok
> t/rtmpdownloader.t ....... ok
> t/title_to_filename.t .... ok
> t/url.t .................. skipped: Not going online, set SITE to run these tests
> t/utils.t ................ ok
> 
> Test Summary Report
> -------------------
> t/google_video_search.t (Wstat: 65280 Tests: 0 Failed: 0)
>   Non-zero exit status: 255
>   Parse errors: Bad plan.  You planned 2 tests but ran 0.
> Files=8, Tests=78,  2 wallclock secs ( 0.07 usr  0.05 sys +  0.86 cusr  0.22 csys =  1.20 CPU)
> Result: FAIL
> Failed 1/8 test programs. 0/78 subtests failed.
> make[1]: *** [test_dynamic] Error 255
> make[1]: Leaving directory `/«PKGBUILDDIR»'
> dh_auto_test: make -j1 test returned exit code 2

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/06/20/get-flash-videos_1.25~git2012.06.27-1_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.