Skip Menu |

This queue is for tickets about the SPVM CPAN distribution.

Report information
The Basics
Id: 124384
Status: resolved
Priority: 0/
Queue: SPVM

People
Owner: Nobody in particular
Requestors: SREZIC [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in:
  • 0.0309
  • 0.0310
  • 0.0311
  • 0.0312
Fixed in: (no value)



Subject: SEGV & ABRT with 0.0309
Many of the jit tests (on some systems all) fail on most my linux smokers (debian/jessie, debian/stretch, Ubuntu 16.04) with segmentation faults or aborts: ... t/jit/array.t ................. All 15 subtests passed # Failed test at t/jit/call-sub.t line 34. # got: 'TestCase::call_sub_byte_array' # expected: '6' # Looks like you failed 1 test of 32. t/jit/call-sub.t .............. Failed 1/32 subtests # Failed test at t/jit/constant.t line 16. # got: 'TestCase::load_constant_int_min' # expected: '-2147483647' # Looks like you failed 1 test of 49. t/jit/constant.t .............. Failed 1/49 subtests ... (etc) ... Test Summary Report ------------------- t/jit/array.t (Wstat: 11 Tests: 15 Failed: 0) Non-zero wait status: 11 t/jit/call-sub.t (Wstat: 11 Tests: 32 Failed: 1) Failed test: 1 Non-zero wait status: 11 t/jit/constant.t (Wstat: 11 Tests: 49 Failed: 1) Failed test: 1 Non-zero wait status: 11 ... t/jit/lib-Arrays.t (Wstat: 6 Tests: 1 Failed: 0) Non-zero wait status: 6 Parse errors: No plan found in TAP output ... (etc) ...
On 2018-02-10 01:18:24, SREZIC wrote: Show quoted text
> Many of the jit tests (on some systems all) fail on most my linux > smokers (debian/jessie, debian/stretch, Ubuntu 16.04) with > segmentation faults or aborts: > > ... > t/jit/array.t ................. > All 15 subtests passed > > # Failed test at t/jit/call-sub.t line 34. > # got: 'TestCase::call_sub_byte_array' > # expected: '6' > # Looks like you failed 1 test of 32. > t/jit/call-sub.t .............. > Failed 1/32 subtests > > # Failed test at t/jit/constant.t line 16. > # got: 'TestCase::load_constant_int_min' > # expected: '-2147483647' > # Looks like you failed 1 test of 49. > t/jit/constant.t .............. > Failed 1/49 subtests > ... (etc) ... > Test Summary Report > ------------------- > t/jit/array.t (Wstat: 11 Tests: 15 Failed: 0) > Non-zero wait status: 11 > t/jit/call-sub.t (Wstat: 11 Tests: 32 Failed: 1) > Failed test: 1 > Non-zero wait status: 11 > t/jit/constant.t (Wstat: 11 Tests: 49 Failed: 1) > Failed test: 1 > Non-zero wait status: 11 > ... > t/jit/lib-Arrays.t (Wstat: 6 Tests: 1 Failed: 0) > Non-zero wait status: 6 > Parse errors: No plan found in TAP output > ... (etc) ...
There are still problems with 0.0310. Test summary on a debian/stretch system, perl 5.24.3: Test Summary Report ------------------- t/jit/call-sub.t (Wstat: 256 Tests: 32 Failed: 1) Failed test: 1 Non-zero exit status: 1 t/jit/constant.t (Wstat: 256 Tests: 49 Failed: 1) Failed test: 1 Non-zero exit status: 1 t/jit/loop.t (Wstat: 256 Tests: 2 Failed: 1) Failed test: 1 Non-zero exit status: 1 t/jit/numeric-operator.t (Wstat: 11 Tests: 45 Failed: 0) Non-zero wait status: 11 t/jit/object.t (Wstat: 11 Tests: 0 Failed: 0) Non-zero wait status: 11 t/jit/string.t (Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Files=67, Tests=1240, 50 wallclock secs ( 0.21 usr 0.20 sys + 23.84 cusr 20.78 csys = 45.03 CPU) Result: FAIL
On 2018-02-10 01:18:24, SREZIC wrote: Show quoted text
> Many of the jit tests (on some systems all) fail on most my linux > smokers (debian/jessie, debian/stretch, Ubuntu 16.04) with > segmentation faults or aborts: > > ... > t/jit/array.t ................. > All 15 subtests passed > > # Failed test at t/jit/call-sub.t line 34. > # got: 'TestCase::call_sub_byte_array' > # expected: '6' > # Looks like you failed 1 test of 32. > t/jit/call-sub.t .............. > Failed 1/32 subtests > > # Failed test at t/jit/constant.t line 16. > # got: 'TestCase::load_constant_int_min' > # expected: '-2147483647' > # Looks like you failed 1 test of 49. > t/jit/constant.t .............. > Failed 1/49 subtests > ... (etc) ... > Test Summary Report > ------------------- > t/jit/array.t (Wstat: 11 Tests: 15 Failed: 0) > Non-zero wait status: 11 > t/jit/call-sub.t (Wstat: 11 Tests: 32 Failed: 1) > Failed test: 1 > Non-zero wait status: 11 > t/jit/constant.t (Wstat: 11 Tests: 49 Failed: 1) > Failed test: 1 > Non-zero wait status: 11 > ... > t/jit/lib-Arrays.t (Wstat: 6 Tests: 1 Failed: 0) > Non-zero wait status: 6 > Parse errors: No plan found in TAP output > ... (etc) ...
Probably fixed in later versions.