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

Are RT todo's still current? #528

Open
JJ opened this issue Apr 15, 2019 · 1 comment
Open

Are RT todo's still current? #528

JJ opened this issue Apr 15, 2019 · 1 comment

Comments

@JJ
Copy link
Contributor

JJ commented Apr 15, 2019

This one, for instance:

https://github.com/perl6/roast/blob/2288d4a3c543d72f822164dad529066ed055a0aa/S04-statements/lazy.t#L14

It does seem to have been implemented already: rakudo/rakudo@d043961

Plus that test does not seem to work:

1..10
No such method 'lazy' for invocant of type 'Int'. Did you mean any of these?
    any
    say

  in block <unit> at S04-statements/lazy.rakudo.moar line 12

# Looks like you planned 10 tests, but ran 0
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 10/10 subtests 

Test Summary Report
-------------------
S04-statements/lazy.rakudo.moar (Wstat: 65280 Tests: 0 Failed: 0)
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 10 tests but ran 0.
Files=1, Tests=0,  0 wallclock secs ( 0.02 usr  0.00 sys +  0.47 cusr  0.02 csys =  0.51 CPU)
Result: FAIL
@usev6
Copy link
Contributor

usev6 commented Apr 15, 2019

In general, I assume (hope) that most RT todo's are still current.

The test file you mentioned is kind of special, since it's not part of Rakudo's t/spectest.data and as such it's never run during spectest or stresstest. I wouldn't put too much trust in tests and RT todo's from such test files. Probably such test files are in need of review from the right persons.

Just my two cents.

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