Skip Menu |

This queue is for tickets about the Test-ShellScript CPAN distribution.

Report information
The Basics
Id: 56896
Status: resolved
Priority: 0/
Queue: Test-ShellScript

People
Owner: Nobody in particular
Requestors: APOCAL [...] cpan.org
Cc:
AdminCc:

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



Subject: This module's testsuite FAILs on MSWin32
Hello, I'm running a CPANTesters smokefarm and saw this module's testsuite hanging on my WinXP VM. The problem was that windows popped up a dialog saying "choose the program you want to use to open this file" for run.sh Obviously, windows doesn't have native support for shell files! Maybe you can modify the testsuite so it skips if $^O eq 'MSWin32' or something like that. Or you could include that in the Makefile.PL/Build.PL and bail out if it detects MSWin32... ( note: cygwin will work just fine, and it's a completely different $^O so you don't have to worry about that :) Thanks again for your work on this module! -- ~Apocalypse
Hello, thanks for reporting this bug (and sorry, have no MSWin32 platform to test on :-P) I made some modifications to let the test to run on this platform. Please download this file [1], decompress it on a folder, run 'perl MakeFile.pl', 'gmake' and 'gmake test' and paste te output here. BTW on 0.03 I added some testing on undef parameters because of your MSWin32 report :-D [1] http://bit-tools.googlecode.com/files/Test-ShellScript- 0.04.mswin32.tar.gz On Sat Apr 24 16:18:09 2010, APOCAL wrote: Show quoted text
> Hello, > > I'm running a CPANTesters smokefarm and saw this module's testsuite > hanging on my WinXP VM. The problem was that windows popped up a
dialog Show quoted text
> saying "choose the program you want to use to open this file" for
run.sh Show quoted text
> > Obviously, windows doesn't have native support for shell files! Maybe > you can modify the testsuite so it skips if $^O eq 'MSWin32' or > something like that. Or you could include that in the > Makefile.PL/Build.PL and bail out if it detects MSWin32... ( note: > cygwin will work just fine, and it's a completely different $^O so you > don't have to worry about that :) > > Thanks again for your work on this module!
Subject: Re: [rt.cpan.org #56896] This module's testsuite FAILs on MSWin32
Date: Sat, 24 Apr 2010 17:39:39 -0700
To: bug-Test-ShellScript [...] rt.cpan.org
From: "perl [...] 0ne.us" <perl [...] 0ne.us>
Hello, Thanks for the quick turnaround! btw, it's "dmake" when you use Strawberry perl :) Hope this helps you find the final answer! C:\cpansmoke\Test-ShellScript-0.04.mswin32>dir Volume in drive C has no label. Volume Serial Number is 1071-BD47 Directory of C:\cpansmoke\Test-ShellScript-0.04.mswin32 04/24/2010 05:35 PM <DIR> . 04/24/2010 05:35 PM <DIR> .. 04/24/2010 03:48 PM 1,240 Changes 04/24/2010 05:35 PM <DIR> lib 04/24/2010 10:50 AM 571 Makefile.PL 04/24/2010 03:45 PM 223 MANIFEST 04/21/2010 09:36 PM 730 README 04/24/2010 05:35 PM <DIR> samples 04/24/2010 05:35 PM <DIR> t 04/24/2010 06:13 AM 486 TODO 5 File(s) 3,250 bytes 5 Dir(s) 22,033,698,816 bytes free C:\cpansmoke\Test-ShellScript-0.04.mswin32>perl Makefile.PL Checking if your kit is complete... Looks good Writing Makefile for Test::ShellScript C:\cpansmoke\Test-ShellScript-0.04.mswin32>dmake cp lib/Test/ShellScript.pm blib\lib\Test\ShellScript.pm C:\cpansmoke\Test-ShellScript-0.04.mswin32>dmake test C:\bootperl\perl\bin\perl.exe "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib\lib', 'blib\arch')" t/*.t t/command_validation.t ....... ok t/compat_TestMore.t .......... ok t/compat_TestMore_no_plan.t .. ok t/run_continous.t ............ 1/? # Failed test ''output' = 'enough_windows_for_me_just_a_test'' # at C:\cpansmoke\Test-ShellScript-0.04.mswin32\blib\lib/Test/ShellScript.pm line 381. # Looks like you failed 1 test of 7. t/run_continous.t ............ Dubious, test returned 1 (wstat 256, 0x100) Failed 1/7 subtests t/run_step_by_step.t ......... 1/? # Failed test 'Current value is 'enough_windows_for_me_just_a_test'' # at C:\cpansmoke\Test-ShellScript-0.04.mswin32\blib\lib/Test/ShellScript.pm line 320. # Looks like you failed 1 test of 11. t/run_step_by_step.t ......... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/11 subtests Test Summary Report ------------------- t/run_continous.t (Wstat: 256 Tests: 7 Failed: 1) Failed test: 7 Non-zero exit status: 1 t/run_step_by_step.t (Wstat: 256 Tests: 11 Failed: 1) Failed test: 11 Non-zero exit status: 1 Files=5, Tests=29, 0 wallclock secs ( 0.03 usr + 0.01 sys = 0.05 CPU) Result: FAIL Failed 2/5 test programs. 2/29 subtests failed. dmake: Error code 129, while making 'test_dynamic' C:\cpansmoke\Test-ShellScript-0.04.mswin32> Victor A. Rodriguez via RT wrote: Show quoted text
> <URL: https://rt.cpan.org/Ticket/Display.html?id=56896 > > > Hello, > > thanks for reporting this bug (and sorry, have no MSWin32 platform to > test on :-P) > > I made some modifications to let the test to run on this platform. > Please download this file [1], decompress it on a folder, run 'perl > MakeFile.pl', 'gmake' and 'gmake test' and paste te output here. > > BTW on 0.03 I added some testing on undef parameters because of your > MSWin32 report :-D > > [1] http://bit-tools.googlecode.com/files/Test-ShellScript- > 0.04.mswin32.tar.gz > > On Sat Apr 24 16:18:09 2010, APOCAL wrote: >
>> Hello, >> >> I'm running a CPANTesters smokefarm and saw this module's testsuite >> hanging on my WinXP VM. The problem was that windows popped up a >>
> dialog >
>> saying "choose the program you want to use to open this file" for >>
> run.sh >
>> Obviously, windows doesn't have native support for shell files! Maybe >> you can modify the testsuite so it skips if $^O eq 'MSWin32' or >> something like that. Or you could include that in the >> Makefile.PL/Build.PL and bail out if it detects MSWin32... ( note: >> cygwin will work just fine, and it's a completely different $^O so you >> don't have to worry about that :) >> >> Thanks again for your work on this module! >>
> > > >
Oppps, a little typo on samples/run.bat where it says echo TEST: output=enough_windows_for_me_just_a_test change it to echo TEST: output=0 and every test will pass. I guess that v0.04 will be available on Monday/Tuesday. Thanks again for your help ! On Sat Apr 24 20:39:52 2010, perl@0ne.us wrote: Show quoted text
> Hello, > > Thanks for the quick turnaround! btw, it's "dmake" when you use > Strawberry perl :) > > Hope this helps you find the final answer! > > C:\cpansmoke\Test-ShellScript-0.04.mswin32>dir > Volume in drive C has no label. > Volume Serial Number is 1071-BD47 > > Directory of C:\cpansmoke\Test-ShellScript-0.04.mswin32 > > 04/24/2010 05:35 PM <DIR> . > 04/24/2010 05:35 PM <DIR> .. > 04/24/2010 03:48 PM 1,240 Changes > 04/24/2010 05:35 PM <DIR> lib > 04/24/2010 10:50 AM 571 Makefile.PL > 04/24/2010 03:45 PM 223 MANIFEST > 04/21/2010 09:36 PM 730 README > 04/24/2010 05:35 PM <DIR> samples > 04/24/2010 05:35 PM <DIR> t > 04/24/2010 06:13 AM 486 TODO > 5 File(s) 3,250 bytes > 5 Dir(s) 22,033,698,816 bytes free > C:\cpansmoke\Test-ShellScript-0.04.mswin32>perl Makefile.PL > Checking if your kit is complete... > Looks good > Writing Makefile for Test::ShellScript > > C:\cpansmoke\Test-ShellScript-0.04.mswin32>dmake > cp lib/Test/ShellScript.pm blib\lib\Test\ShellScript.pm > > C:\cpansmoke\Test-ShellScript-0.04.mswin32>dmake test > C:\bootperl\perl\bin\perl.exe "-MExtUtils::Command::MM" "-e" > "test_harness(0, 'blib\lib', 'blib\arch')" t/*.t > t/command_validation.t ....... ok > t/compat_TestMore.t .......... ok > t/compat_TestMore_no_plan.t .. ok > t/run_continous.t ............ 1/? > # Failed test ''output' = 'enough_windows_for_me_just_a_test'' > # at C:\cpansmoke\Test-ShellScript- > 0.04.mswin32\blib\lib/Test/ShellScript.pm line 381. > # Looks like you failed 1 test of 7. > t/run_continous.t ............ Dubious, test returned 1 (wstat 256, > 0x100) > Failed 1/7 subtests > t/run_step_by_step.t ......... 1/? > # Failed test 'Current value is 'enough_windows_for_me_just_a_test'' > # at C:\cpansmoke\Test-ShellScript- > 0.04.mswin32\blib\lib/Test/ShellScript.pm line 320. > # Looks like you failed 1 test of 11. > t/run_step_by_step.t ......... Dubious, test returned 1 (wstat 256, > 0x100) > Failed 1/11 subtests > > Test Summary Report > ------------------- > t/run_continous.t (Wstat: 256 Tests: 7 Failed: 1) > Failed test: 7 > Non-zero exit status: 1 > t/run_step_by_step.t (Wstat: 256 Tests: 11 Failed: 1) > Failed test: 11 > Non-zero exit status: 1 > Files=5, Tests=29, 0 wallclock secs ( 0.03 usr + 0.01 sys = 0.05 > CPU) > Result: FAIL > Failed 2/5 test programs. 2/29 subtests failed. > dmake: Error code 129, while making 'test_dynamic' > > C:\cpansmoke\Test-ShellScript-0.04.mswin32> > > > Victor A. Rodriguez via RT wrote:
> > <URL: https://rt.cpan.org/Ticket/Display.html?id=56896 > > > > > Hello, > > > > thanks for reporting this bug (and sorry, have no MSWin32 platform
> to
> > test on :-P) > > > > I made some modifications to let the test to run on this platform. > > Please download this file [1], decompress it on a folder, run 'perl > > MakeFile.pl', 'gmake' and 'gmake test' and paste te output here. > > > > BTW on 0.03 I added some testing on undef parameters because of your > > MSWin32 report :-D > > > > [1] http://bit-tools.googlecode.com/files/Test-ShellScript- > > 0.04.mswin32.tar.gz > > > > On Sat Apr 24 16:18:09 2010, APOCAL wrote: > >
> >> Hello, > >> > >> I'm running a CPANTesters smokefarm and saw this module's
> testsuite
> >> hanging on my WinXP VM. The problem was that windows popped up a > >>
> > dialog > >
> >> saying "choose the program you want to use to open this file" for > >>
> > run.sh > >
> >> Obviously, windows doesn't have native support for shell files!
> Maybe
> >> you can modify the testsuite so it skips if $^O eq 'MSWin32' or > >> something like that. Or you could include that in the > >> Makefile.PL/Build.PL and bail out if it detects MSWin32... ( note: > >> cygwin will work just fine, and it's a completely different $^O so
> you
> >> don't have to worry about that :) > >> > >> Thanks again for your work on this module! > >>
> > > > > > > >
I've just uploaded v0.04 to CPAN. Tested on Wine/Linux and it run OK. :-)
Glad to be of help! :) -- ~Apocalypse