> From: Konovalov, Vadim > Sent: Monday, July 9, 2018 10:04 AM > Have anyone reproduce of this, or explanation on what could cause this? > > http://www.cpantesters.org/cpan/report/29e842b4-8019-11e8-9bb2-e7af5549a355 > > ... > Output from '/usr/bin/make test': > > PERL_DL_NONLAZY=1 > "/opt/perl-5.28.0t/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" > "undef *Test::Harness::Switches; test_harness(0, 'blib/lib', 'blib/arch')" > t/*.t Tcl procedure 'winfo' not found at > /home/cpansand/.cpan/build/2018070505/Tcl-Tk-1.10-11/blib/lib/Tcl/Tk.pm line > 575. > t/after.t ....... > Dubious, test returned 2 (wstat 512, 0x200) Failed 6/6 > subtests ... etc > > It looks like failure to load Tk package (wrong DISPLAY var?) > - but then - how this passed Makefile.PL check?
Indeed removing DISPLAY variable during test could be reason of this. konovv@RUENKONOVVL2C ~/p-dev/perl-tcl-tk $ make test PERL_DL_NONLAZY=1 "/usr/bin/perl.exe" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0, 'blib/lib', 'blib/arch')" t/*.t t/after.t ....... ok t/canvas.t ...... ok t/geomgr.t ...... ok t/optmenu.t ..... skipped: no snit extension available t/photo.t ....... skipped: no Img extension available (can't find package Img at /cygdrive/c/vad/perl-dev/perl-tcl-tk/blib/lib/Tcl/Tk.pm line 748. t/ptk-compat.t .. ok t/text.t ........ skipped: no snit extension available t/tk-mw.t ....... ok t/unicode.t ..... ok t/zzPhoto.t ..... skipped: no Img extension available All tests successful. Files=10, Tests=36, 23 wallclock secs ( 0.01 usr 0.25 sys + 3.74 cusr 3.57 csys = 7.58 CPU) Result: PASS konovv@RUENKONOVVL2C ~/p-dev/perl-tcl-tk $ DISPLAY= make test PERL_DL_NONLAZY=1 "/usr/bin/perl.exe" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0, 'blib/lib', 'blib/arch')" t/*.t t/after.t ....... Tcl procedure 'winfo' not found at /cygdrive/c/vad/perl-dev/perl-tcl-tk/blib/lib/Tcl/Tk.pm line 575. t/after.t ....... Dubious, test returned 3 (wstat 768, 0x300) Failed 6/6 subtests Any ideas how to avoid such FAIL reports?
