# New Ticket Created by A. Sinan Unur # Please include the string: [perl #130788] # in the subject line of all future correspondence about this issue. # <URL: https://rt.perl.org/Ticket/Display.html?id=130788 >
$ perl t\harness5 t\spec\S17-procasync\basic.rakudo.moar --verbosity=5 ... not ok 33 - Tapping stdout supply after start of process does not lose data # Failed test 'Tapping stdout supply after start of process does not lose data' # at t\spec\S17-procasync\basic.rakudo.moar line 109 # expected: "Hello World\n" # got: "Hello World\r\n" ok 34 - Process that doesn't output anything will not emit # FUDGED! # Looks like you failed 1 test of 34 Dubious, test returned 1 (wstat 256, 0x100) For text streams, the standard way of dealing with differing EOL conversions is to convert "\n" to the platform specific EOL sequence on output and convert the platform specific EOL sequence to "\n" on input. It looks like that is not being done in Proc::Async or whatever plumbing it depends on. See also https://www.nu42.com/2015/12/perl6-newline-behavior-fixed.html and https://github.com/perl6/roast/issues/232#issuecomment-280061047 -- Sinan
