Skip to content

Instantly share code, notes, and snippets.

@FROGGS
Last active August 29, 2015 14:05
Show Gist options
  • Save FROGGS/80b086660badcf365e5a to your computer and use it in GitHub Desktop.
Save FROGGS/80b086660badcf365e5a to your computer and use it in GitHub Desktop.
Test Summary Report
-------------------
t/spec/S03-operators/context.t (Wstat: 1024 Tests: 36 Failed: 4)
Failed tests: 30-33
Non-zero exit status: 4
t/spec/S32-exceptions/misc.rakudo.moar (Wstat: 139 Tests: 114 Failed: 1)
Failed test: 114
Non-zero wait status: 139
Parse errors: Bad plan. You planned 263 tests but ran 114.
t/spec/S32-list/uniq.rakudo.moar (Wstat: 139 Tests: 24 Failed: 0)
Non-zero wait status: 139
Parse errors: Bad plan. You planned 33 tests but ran 24.
t/spec/integration/99problems-51-to-60.t (Wstat: 139 Tests: 20 Failed: 0)
Non-zero wait status: 139
Parse errors: Bad plan. You planned 37 tests but ran 20.
t/spec/integration/advent2010-day12.t (Wstat: 65280 Tests: 7 Failed: 0)
Non-zero exit status: 255
Parse errors: Bad plan. You planned 13 tests but ran 7.
Files=915, Tests=32906, 402 wallclock secs ( 9.33 usr 1.35 sys + 974.53 cusr 83.02 csys = 1068.23 CPU)
Result: FAIL
Test Summary Report
-------------------
t/spec/S03-operators/context.t (Wstat: 1024 Tests: 36 Failed: 4)
Failed tests: 30-33
Non-zero exit status: 4
t/spec/S17-lowlevel/lock.rakudo.moar (Wstat: 256 Tests: 8 Failed: 1)
Failed test: 7
Non-zero exit status: 1
t/spec/S32-exceptions/misc.rakudo.moar (Wstat: 139 Tests: 114 Failed: 1)
Failed test: 114
Non-zero wait status: 139
Parse errors: Bad plan. You planned 264 tests but ran 114.
t/spec/S32-list/uniq.rakudo.moar (Wstat: 139 Tests: 26 Failed: 0)
Non-zero wait status: 139
Parse errors: Bad plan. You planned 33 tests but ran 26.
t/spec/integration/99problems-51-to-60.t (Wstat: 139 Tests: 20 Failed: 0)
Non-zero wait status: 139
Parse errors: Bad plan. You planned 37 tests but ran 20.
Files=915, Tests=32914, 511 wallclock secs (10.90 usr 1.51 sys + 1156.51 cusr 90.51 csys = 1259.43 CPU)
Result: FAIL
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment