Front page | perl.perl5.porters |
Postings from July 2017
On 07/07/2017 01:07 PM, Karl Williamson wrote: > On 07/02/2017 12:02 PM, Dave Mitchell wrote: >> On Sun, Jul 02, 2017 at 09:54:11AM -0600, Karl Williamson wrote: >>> I just got it again: >>> >>> # Failed test 29 - croak: cachegrind output format at >>> porting/bench.t line >>> 349 >>> # got 'Error: call::sub::empty/A empty/short loop gave return >>> status >>> 0x7f0 0\nwith the following output\n:valgrind: Boz: command not >>> found\n\n' >>> # expected /(?^:Error: while executing call::sub::empty/A empty/short >>> loop:\nun expected code or cachegrind output:\n)/ >>> >>> but this is only the 2nd or 3rd time in hundreds of runs. Is there a >>> way to >>> change the default on this so when it does crop up again we'll have >>> the data >>> you need? >> >> Just done with v5.27.1-95-g132771f >> > > This is what I got: > > # Failed test 29 - croak: cachegrind output format at porting/bench.t > line 349 > # got 'Main loop: pending=8 running=0\nError: call::sub::empty/A > empty/short loop gave return status 0x7f00\nwith the following > output\n:valgrind: Boz: command not found\n\nStarted pid 32288 for > call::sub::empty/A empty/short loop\nSelect: waiting on (32288)\nSelect: > pids (32288) ready\n' > # expected /(?^:Error: while executing call::sub::empty/A empty/short > loop:\nunexpected code or cachegrind output:\n)/ > # Failed test 29 - croak: cachegrind output format at porting/bench.t line 349 # got 'Main loop: pending=8 running=0\nError: call::sub::empty/A empty/short loop gave return status 0x7f00\nwith the following output\n:valgrind: Boz: command not found\n\nStarted pid 2669 for call::sub::empty/A empty/short loop\nSelect: waiting on (2669)\nSelect: pids (2669) ready\n' # expected /(?^:Error: while executing call::sub::empty/A empty/short loop:\nunexpected code or cachegrind output:\n)/ which is effectively the same; so I won't bother to email any future ones unless there is a changeThread Previous | Thread Next