Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bailador test failures in Rakudo Star #19

Closed
pmichaud opened this issue Mar 17, 2013 · 1 comment
Closed

Bailador test failures in Rakudo Star #19

pmichaud opened this issue Mar 17, 2013 · 1 comment

Comments

@pmichaud
Copy link
Contributor

Rakudo Star 2013.02 fails modules-test in Bailador. This needs to be fixed prior to the 2013.03 release.

Testing modules/Bailador...
t/01-route-existance.t ... ok   
t/02-response-status.t ... ok   
t/03-response-content.t .. 2/7 Not enough positional parameters passed; got 0 but expected 1
  in sub  at t/03-response-content.t:12
  in block  at /zip/perl/rakudo-star-2013.02/install/lib/parrot/4.10.0/languages/perl6/lib/Bailador.pm:84
  in sub dispatch at /zip/perl/rakudo-star-2013.02/install/lib/parrot/4.10.0/languages/perl6/lib/Bailador.pm:80
  in sub dispatch_request at /zip/perl/rakudo-star-2013.02/install/lib/parrot/4.10.0/languages/perl6/lib/Bailador.pm:72
  in sub get-response at /zip/perl/rakudo-star-2013.02/install/lib/parrot/4.10.0/languages/perl6/lib/Bailador/Test.pm:9
  in sub response-content-is at /zip/perl/rakudo-star-2013.02/install/lib/parrot/4.10.0/languages/perl6/lib/Bailador/Test.pm:33
  in block  at t/03-response-content.t:21

t/03-response-content.t .. Dubious, test returned 1 (wstat 256, 0x100)
Failed 3/7 subtests 
t/04-templates.t ......... ok   
t/05-post-content.t ...... ok   

Test Summary Report
-------------------
t/03-response-content.t (Wstat: 256 Tests: 4 Failed: 0)
  Non-zero exit status: 1
  Parse errors: Bad plan.  You planned 7 tests but ran 4.
Files=5, Tests=16,  6 wallclock secs ( 0.05 usr  0.02 sys +  5.02 cusr  0.76 csys =  5.85 CPU)
Result: FAIL
@tadzik
Copy link

tadzik commented Apr 30, 2013

It works correctly now, so the issue is fixed.

@tadzik tadzik closed this as completed Apr 30, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants