Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.0(EOL), 10.1(EOL), 10.2(EOL)
-
None
-
kvm-fulltest --ps-protocol
Description
http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest/builds/8688/steps/test_3/logs/stdio
unit.lf w4 [ fail ]
|
Test ended at 2017-05-08 08:42:15
|
|
CURRENT_TEST: unit.lf
|
# N CPUs: 4, atomic ops: gcc-atomics-smp
|
1..7
|
ok 1 - my_atomic_initialize() returned 0
|
# Testing lf_pinbox (with my_thread_init) with 30 threads, 3000 iterations...
|
Bail out! Signal 11 thrown
|
# 7 tests planned, 0 failed, 1 was last executed
|
|
|
mysqltest failed with unexpected return code 255
|
Attachments
Issue Links
- duplicates
-
MDEV-15670 unit.my_atomic failed in buildbot with Signal 11 thrown
-
- Closed
-
- is duplicated by
-
MDEV-14465 unit.lf failed in buildbot, sporadic
-
- Closed
-
- relates to
-
MDEV-27088 Server crash on ARM (WMM architecture) due to missing barriers in lf-hash
-
- Closed
-
-
MDEV-28430 lf_alloc isn't safe on aarch64 (or ppc64le)
-
- Closed
-
10.0 8d0448d5075fe822e37f81b740e83f03
unit.lf w1 [ fail ]
Test ended at 2017-09-21 18:16:15
CURRENT_TEST: unit.lf
# N CPUs: 4, atomic ops: gcc-atomics-smp
1..7
ok 1 - my_atomic_initialize() returned 0
# Testing lf_pinbox (with my_thread_init) with 30 threads, 3000 iterations...
ok 2 - tested lf_pinbox (with my_thread_init) in 0.0290057 secs (0)
# Testing lf_alloc (with my_thread_init) with 30 threads, 3000 iterations...
# 0 mallocs, 17 pins in stack
ok 3 - tested lf_alloc (with my_thread_init) in 0.0487313 secs (0)
# Testing lf_hash (with my_thread_init) with 30 threads, 300 iterations...
Bail out! Signal 11 thrown
# 7 tests planned, 0 failed, 3 was last executed
mysqltest failed with unexpected return code 255