On Thu, 30 May 2013 08:58:50 -0700, "Will Coleda via RT" wrote:
> On Wed, May 29, 2013 at 10:29 AM, Pascal Stumpf <[email protected]>wrote:
>
> > On Wed, 29 May 2013 05:42:27 -0700, "Will Coleda via RT" wrote:
> > > How are you running the spec tests? - it looks like you've included some
> > > that are not marked as runnable by rakudo.
> >
> > I think I did a "gmake spectest_full". Shall I run just the spectest
> > target again or can you just ignore the tests that are not marked as
> > runnable?
>
>
> spectest_full is only useful if you're a developer looking for more tests
> to run.
>
> If you could rerun with just 'gmake spectest' that'll give us a much better
> idea of what's actually broken. And for those tests that fail, please
> provide the verbose output when running each of those test files.
>
> You can get verbose output for a single test file with: 'make
> t/spec/S02-types/bool.t'
>
> Thanks.
Hi,
here's the test summary and output from failed tests:
Test Summary Report
-------------------
t/spec/S02-literals/char-by-name.rakudo (Wstat: 256 Tests: 0
Failed: 0)
Non-zero exit status: 1
Parse errors: No plan found in TAP output
t/spec/S03-operators/arith.rakudo (Wstat: 0 Tests: 143
Failed: 1)
Failed test: 112
t/spec/S05-mass/named-chars.rakudo (Wstat: 256 Tests: 0
Failed: 0)
Non-zero exit status: 1
Parse errors: No plan found in TAP output
t/spec/S05-mass/properties-block.rakudo (Wstat: 256 Tests: 0
Failed: 0)
Non-zero exit status: 1
Parse errors: No plan found in TAP output
t/spec/S05-mass/properties-derived.rakudo (Wstat: 256 Tests: 0
Failed: 0)
Non-zero exit status: 1
Parse errors: No plan found in TAP output
t/spec/S05-mass/properties-general.rakudo (Wstat: 256 Tests: 0
Failed: 0)
Non-zero exit status: 1
Parse errors: No plan found in TAP output
t/spec/S19-command-line/dash-e.t (Wstat: 0 Tests: 3
Failed: 2)
Failed tests: 2-3
t/spec/S32-hash/delete-adverb.rakudo (Wstat: 0 Tests: 108
Failed: 0)
TODO passed: 17, 22-23, 25, 28-29, 31, 34-37, 39, 54
68
t/spec/S32-num/int.rakudo (Wstat: 256 Tests: 86
Failed: 0)
Non-zero exit status: 1
Parse errors: Bad plan. You planned 107 tests but ran 86.
t/spec/S32-num/power.rakudo (Wstat: 0 Tests: 50
Failed: 1)
Failed test: 18
Files=738, Tests=25798, 5896 wallclock secs (11.98 usr 118.69 sys + 4175.85
cusr 1257.87 csys = 5564.39 CPU)
Result: FAIL
t/spec/S03-operators/arith.rakudo ..
1..143
ok 1 - 1 == 1
ok 2 - 3 == 3
ok 3 - -3 == -3
ok 4 - -1 == -1
ok 5 - 1 == 1
ok 6 - 3 == 3
ok 7 - -3 == -3
ok 8 - -1 == -1
ok 9 - 0 == 0
ok 10 - 0.5 == 0.5
ok 11 - modulo with negative divisor (1)
ok 12 - modulo with negative divisor (2)
ok 13 -
ok 14 -
ok 15 -
ok 16 -
ok 17 - 2 == 2
ok 18 - 2 == 2
ok 19 - 90 == 90
ok 20 - -16 == -16
ok 21 - -61 == -61
ok 22 - 3 == 3
ok 23 - 0 == 0
ok 24 - 0 == 0
ok 25 - 3 == 3
ok 26 - -13 == -13
ok 27 - 2 == 2
ok 28 - -12 == -12
ok 29 - 10 == 10
ok 30 - -161 == -161
ok 31 - -151 == -151
ok 32 - 7 == 7
ok 33 - 0 == 0
ok 34 - 0 == 0
ok 35 - 2147483647 == 2147483647
ok 36 - 2147483647 == 2147483647
ok 37 - 1 == 1
ok 38 - -1 == -1
ok 39 - 4294967290 == 4294967290
ok 40 - -4294967290 == -4294967290
ok 41 - 4294967297 == 4294967297
ok 42 - -4294967297 == -4294967297
ok 43 - -1 == -1
ok 44 - 1 == 1
ok 45 - 4294967290 == 4294967290
ok 46 - -4294967290 == -4294967290
ok 47 - -4294967297 == -4294967297
ok 48 - 4294967297 == 4294967297
ok 49 - 3 == 3
ok 50 - -6 == -6
ok 51 - -9 == -9
ok 52 - 12 == 12
ok 53 - 2147395599 == 2147395599
ok 54 - -2147395599 == -2147395599
ok 55 - -2147395599 == -2147395599
ok 56 - 2147395599 == 2147395599
ok 57 - 2 == 2
ok 58 - 2 == 2
ok 59 - 1.2 == 1.2
ok 60 - -1.2 == -1.2
ok 61 - 2 == 2
ok 62 - -4 == -4
ok 63 - -7 == -7
ok 64 - 14 == 14
ok 65 - 9 div 4 == 2
not ok 66 - -9 div 4 == -3# TODO negative div
# got: '-2'
# expected: '-3'
not ok 67 - 9 div -4 == -3# TODO negative div
# got: '-2'
# expected: '-3'
ok 68 - -9 div -4 == 2
ok 69 - 13 mod 4
not ok 70 - -13 mod 4# TODO negative mod
# got: '-1'
# expected: '3'
not ok 71 - 13 mod -4# TODO negative mod
# got: '1'
# expected: '-3'
ok 72 - -13 mod -4
ok 73 - 1.25 == 1.25
ok 74 - -1.75 == -1.75
ok 75 - -2.25 == -2.25
ok 76 - 2.75 == 2.75
ok 77 -
ok 78 -
ok 79 -
ok 80 -
ok 81 -
ok 82 -
ok 83 - ** is right associative
ok 84 - infix:<**> is right associative
ok 85 - i^2 == -1
ok 86 - sqrt(-i)**4 ==-1
ok 87 - (-1+0i)**0.5 == i
ok 88 -
ok 89 -
ok 90 -
ok 91 -
ok 92 -
ok 93 -
ok 94 -
ok 95 -
ok 96 -
ok 97 -
ok 98 -
ok 99 -
ok 100 -
ok 101 -
ok 102 -
ok 103 -
ok 104 -
ok 105 -
ok 106 -
ok 107 -
ok 108 - 100**Inf
ok 109 - Inf**Inf
ok 110 - 0.9**Inf converges towards 0
ok 111 - 1.1**Inf diverges towards Inf
not ok 112 -
# got: 'NaN'
# expected: '1'
ok 113 -
ok 114 -
ok 115 -
ok 116 -
ok 117 -
ok 118 -
ok 119 -
ok 120 -
ok 121 -
ok 122 -
ok 123 -
ok 124 -
ok 125 -
ok 126 -
ok 127 -
ok 128 -
ok 129 - NaN**NaN
ok 130 - NaN**Inf
ok 131 - Inf**NaN
0
not ok 132 - Modulo zero dies and is catchable# TODO modulo by zero
0
not ok 133 - Modulo zero dies and is catchable with VInt/VRat variables# TODO
modulo by zero
0
not ok 134 - Modulo zero dies and is catchable with VRef variables# TODO die or
fail?
ok 135 - Division by zero dies and is catchable
ok 136 - Division by zero dies and is catchable with VInt div VRat variables
ok 137 - Division by zero dies and is catchable with VRef variables
ok 138 - Can calcualte 25! without loss of precision
ok 139 - Can calcualte 2**65 without loss of precision
ok 140 - no more Rat literals, infix:</> has normal left assoc
ok 141 - infix:<+> is not iffy enough
ok 142 - -Inf warns (and yields 0) but does not give an error
ok 143 - infix:<-> produces a proper Int, even if some of the types invovled
have mixins
# Looks like you failed 1 tests of 143
# FUDGED!
Failed 1/143 subtests
Test Summary Report
-------------------
t/spec/S03-operators/arith.rakudo (Wstat: 0 Tests: 143 Failed: 1)
Failed test: 112
Files=1, Tests=143, 20 wallclock secs ( 0.11 usr 0.04 sys + 12.86 cusr 2.65
csys = 15.66 CPU)
Result: FAIL
t/spec/S19-command-line/dash-e.t ..
1..3
ok 1 - -e print $something works
not ok 2 - -e print $something works with non-ASCII string literals
# got out: "ç"
# expected out: "ȧ"
not ok 3 - -e works with non-ASCII program texts
# got status: 1
# got out: ""
# expected out: "23"
# got err: "\x[1b][31m===\x[1b][0mSORRY!\x[1b][31m===\x[1b][0m\nTwo terms
in a row\nat -e:1\n------> \x[1b][32mprint <1 2>
\x[1b][33mâ\x[1b][31mû+ë <1 1>\x[1b][0m\n expecting any of:\n
postfix\n infix stopper\n infix or meta-infix\n statement
end\n statement modifier\n statement modifier loop\n"
# expected err: ""
# Looks like you failed 2 tests of 3
Failed 2/3 subtests
Test Summary Report
-------------------
t/spec/S19-command-line/dash-e.t (Wstat: 0 Tests: 3 Failed: 2)
Failed tests: 2-3
Files=1, Tests=3, 27 wallclock secs ( 0.05 usr 0.53 sys + 17.48 cusr 7.31
csys = 25.37 CPU)
Result: FAIL
t/spec/S32-num/power.rakudo ..
1..50
ok 1 - 0 ** 0 == 1
ok 2 - 0 ** 1 == 0
ok 3 - 1 ** 2 == 1
ok 4 - 4 ** 0 == 1
ok 5 - 4 ** 1 == 4
ok 6 - 4 ** 2 == 16
ok 7 - 0 ** 4553535345364535345634543534 == 0
ok 8 - 1 ** 4553535345364535345634543534 == 1
not ok 9 - -1 ** 4553535345364535345634543534 == 1# TODO Simple bigint
optimizations NYI
# got: '-Inf'
# expected: '1'
not ok 10 - -1 ** 4553535345364535345634543534 == -1# TODO Simple bigint
optimizations NYI
# got: '-Inf'
# expected: '-1'
ok 11 - 2 ** 4553535345364535345634543534 == Inf
not ok 12 - -2 ** 4553535345364535345634543534 == Inf# TODO Simple bigint
optimizations NYI
# got: '-Inf'
# expected: 'Inf'
ok 13 - -2 ** 4553535345364535345634543534 == -Inf
ok 14 - 4 ** .5 == 2
ok 15 - 4 ** (1/2) == 2
ok 16 - 4 ** (-1/2) == 1/2
ok 17 - -2 ** 2 = 4
not ok 18 - 1**Inf=1
# got: 'NaN'
# expected: '1'
ok 19 - 0**Inf=0
ok 20 - Inf**2 = Inf
ok 21 - (-Inf)**3 = -Inf
ok 22 - Inf**Inf = Inf
ok 23 - NaN propagates with integer powers
ok 24 - NaN propagates with numeric powers
ok 25 - 0**NaN=NaN
ok 26 - # SKIP NaN**1i should be NaN
ok 27 - # SKIP 1i**NaN should be NaN
ok 28 - # SKIP NaN**0 should be NaN
ok 29 - NaN**NaN=NaN
ok 30 - Inf**NaN=NaN
ok 31 - NaN**Inf=NaN
ok 32 - e ** .5 == exp(.5)
ok 33 - e ** 2.5 == exp(2.5)
ok 34 - (4+0i) ** 2 == 16
ok 35 - i ** 4 == 1
ok 36 - (4+0i) ** .5 == 2
ok 37 - i ** 2 == -1
ok 38 - i ** 3 == -i
ok 39 - 5i ** 3 = -125i
ok 40 - 3i ** 3 = -27i
ok 41 - -3i ** 3 = 27i
ok 42 - # SKIP i
ok 43 - quartic root of 8i ** 4 = 8i
ok 44 - quartic root of 8i ** 4 = 8i
ok 45 - quartic root of 8i ** 4 = 8i
ok 46 - quartic root of 8i ** 4 = 8i
ok 47 - e ** pi i = -1
ok 48 - (4+0i) ** (2+0i) == 16
ok 49 - 1.015 ** 200 is not NaN
ok 50 - 1.015 ** 200 == 19.6430286394751
# Looks like you failed 1 tests of 50
# FUDGED!
Failed 1/50 subtests
(less 4 skipped subtests: 45 okay)
Test Summary Report
-------------------
t/spec/S32-num/power.rakudo (Wstat: 0 Tests: 50 Failed: 1)
Failed test: 18
Files=1, Tests=50, 8 wallclock secs ( 0.10 usr 0.41 sys + 5.31 cusr 1.72
csys = 7.54 CPU)
Result: FAIL
Thank you for looking at this!
>
>
> --
> Will "Coke" Coleda
>
>
>
> On Wed, May 29, 2013 at 10:29 AM, Pascal Stumpf
> <[email protected]> wrote:
>
> On Wed, 29 May 2013 05:42:27 -0700, "Will Coleda via RT" wrote:
> > How are you running the spec tests? - it looks like you've
> included some
> > that are not marked as runnable by rakudo.
>
> I think I did a "gmake spectest_full". Ã Shall I run just the
> spectest
> target again or can you just ignore the tests that are not
> marked as
> runnable?
>
> spectest_full is only useful if you're a developer looking for more
> tests to run.
> If you could rerun with just 'gmake spectest' that'll give us a
> much better idea of what's actually broken. And for those tests
> that fail, please provide the verbose output when running each of
> those test files.
> You can get verbose output for a single test file with: 'make
> t/spec/S02-types/bool.t'
> Thanks.Ã
> --
> Will "Coke" Coleda
