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

t/spec/integration/weird-errors. #5150

Closed
p6rt opened this issue Feb 22, 2016 · 5 comments
Closed

t/spec/integration/weird-errors. #5150

p6rt opened this issue Feb 22, 2016 · 5 comments

Comments

@p6rt
Copy link

p6rt commented Feb 22, 2016

Migrated from rt.perl.org#127592 (status was 'resolved')

Searchable as RT127592$

@p6rt
Copy link
Author

p6rt commented Feb 22, 2016

From @coke

This test fails with a release candidate for the 2016.02 branch,
against the 6.c-errata roast branch​:

not ok 20 - appropriate error message instead of internal compiler error

# Failed test 'appropriate error message instead of internal compiler error'
# at /Users/williamcoleda/sandbox/rakudo/t/spec/packages/Test/Util.pm line 58
# got err​: "\x[1b][31m===\x[1b][0mSORRY!\x[1b][31m===\x[1b][0m
Error while compiling
/Users/williamcoleda/sandbox/rakudo/getout-92592-58877.code\nNo such
symbol '​:<>'\nat
/Users/williamcoleda/sandbox/rakudo/getout-92592-58877.code​:1\n------>
\x[1b][32m(​::​:[]\x[1b][33m⏏\x[1b][31m)\x[1b][0m\n"

--
Will "Coke" Coleda

@p6rt
Copy link
Author

p6rt commented Feb 22, 2016

From @moritz

This test could be relaxed. Its main purpose was to check that the compiler didn't crash with an internal error. The input for this test is weird enough that there many ways in which this could be constructed as an error.

@p6rt
Copy link
Author

p6rt commented Apr 11, 2016

From @usev6

The test was relaxed with commit Raku/roast@a069b922c9 (6.c-errata branch).

I'm closing this ticket as 'resolved'.

1 similar comment
@p6rt
Copy link
Author

p6rt commented Apr 11, 2016

From @usev6

The test was relaxed with commit Raku/roast@a069b922c9 (6.c-errata branch).

I'm closing this ticket as 'resolved'.

@p6rt
Copy link
Author

p6rt commented Apr 11, 2016

@usev6 - Status changed from 'new' to 'resolved'

@p6rt p6rt closed this as completed Apr 11, 2016
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

1 participant