[perl #116709] [BUG] Rakudo only passes t/spec/S19-command-line/dash-e.t with a UTF-8 locale

[via RT]

# New Ticket Created by  Nicholas Clark 
# Please include the string:  [perl #116709]
# in the subject line of all future correspondence about this issue. 
# <URL: https://rt.perl.org:443/rt3/Ticket/Display.html?id=116709 >


Compare:

$ LC_ALL=en_US.utf8 ./perl6 -Ilib t/spec/S19-command-line/dash-e.t
1..3
ok 1 - -e print $something works
ok 2 - -e print $something works with non-ASCII string literals
ok 3 - -e works with non-ASCII program texts

$ LC_ALL=C ./perl6 -Ilib 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 or meta-infix\n        infix stopper\n        statement 
end\n        statement modifier\n        statement modifier loop\n"
# expected err: ""
# Looks like you failed 2 tests of 3


My opinion is that the spectest shouldn't *fail* if the locale isn't UTF-8.
Should it be skipping?

(Also, should stderr have all the ANSI escape codes if it's not a tty?
I think that clang changes its behaviour if you capture stderr.)

Nicholas Clark