Export to GitHub

memcached - issue #398

make test failed


Posted on Feb 21, 2015 by Swift Bear

What steps will reproduce the problem?

1. tar zxvf memcached-1.4.22.tar.gz cd memcached-1.4.22 ./configure make make test

meke test is not successful

What is the expected output? What do you see instead?

Finally, following error

t/lru-crawler.t ...... 93/189 Timeout.. killing the process t/lru-crawler.t ...... 96/189

・・・

Looks like you planned 189 tests but ran 188.

Looks like you failed 93 tests of 188 run.

Looks like your test exited with 111 just after 188.

t/lru-crawler.t ...... Dubious, test returned 111 (wstat 28416, 0x6f00) Failed 94/189 subtests t/lru.t .............. ok
t/maxconns.t ......... ok
t/multiversioning.t .. ok
t/noreply.t .......... ok
t/slabs_reassign.t ... ok
t/stats-conns.t ...... ok
t/stats-detail.t ..... ok
t/stats.t ............ ok
t/touch.t ............ ok
t/udp.t .............. ok
t/unixsocket.t ....... ok

Test Summary Report

t/lru-crawler.t (Wstat: 28416 Tests: 188 Failed: 93) Failed tests: 96-188 Non-zero exit status: 111 Parse errors: Bad plan. You planned 189 tests but ran 188. Files=47, Tests=7065, 728 wallclock secs ( 0.94 usr 0.20 sys + 390.82 cusr 47.82 csys = 439.78 CPU) Result: FAIL

What version of the product are you using? On what operating system?

CentOS 6.4 and memcached-1.4.22

Please provide any additional information below.

information below is gdb (gdb) bt

0 0x00007f449d473ef3 in epoll_wait () from /lib64/libc.so.6

1 0x00007f449db67326 in epoll_dispatch (base=0xe90010, tv=<value optimized out>) at epoll.c:407

2 0x00007f449db55ac6 in event_base_loop (base=0xe90010, flags=0) at event.c:1607

3 0x00000000004089b9 in main (argc=<value optimized out>, argv=<value optimized out>) at memcached.c:5638

(gdb) info thread 7 Thread 0x7f449d38a700 (LWP 3668) 0x00007f449d473ef3 in epoll_wait () from /lib64/libc.so.6 6 Thread 0x7f449c989700 (LWP 3669) 0x00007f449d473ef3 in epoll_wait () from /lib64/libc.so.6 5 Thread 0x7f449bf88700 (LWP 3670) 0x00007f449d473ef3 in epoll_wait () from /lib64/libc.so.6 4 Thread 0x7f449b587700 (LWP 3671) 0x00007f449d473ef3 in epoll_wait () from /lib64/libc.so.6 3 Thread 0x7f449ab86700 (LWP 3672) 0x00007f449d72a5bc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 2 Thread 0x7f449a185700 (LWP 3673) 0x00007f449d72a5bc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 * 1 Thread 0x7f449df96700 (LWP 3667) 0x00007f449d473ef3 in epoll_wait () from /lib64/libc.so.6 (gdb) thread 2 [Switching to thread 2 (Thread 0x7f449a185700 (LWP 3673))]#0 0x00007f449d72a5bc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 (gdb) bt

0 0x00007f449d72a5bc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0

1 0x0000000000416cd9 in item_crawler_thread (arg=<value optimized out>) at items.c:807

2 0x00007f449d7269d1 in start_thread () from /lib64/libpthread.so.0

3 0x00007f449d4738fd in clone () from /lib64/libc.so.6

(gdb) thread 3 [Switching to thread 3 (Thread 0x7f449ab86700 (LWP 3672))]#0 0x00007f449d72a5bc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 (gdb) bt

0 0x00007f449d72a5bc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0

1 0x000000000041877b in assoc_maintenance_thread (arg=<value optimized out>) at assoc.c:256

2 0x00007f449d7269d1 in start_thread () from /lib64/libpthread.so.0

3 0x00007f449d4738fd in clone () from /lib64/libc.so.6

(gdb) thread 4 [Switching to thread 4 (Thread 0x7f449b587700 (LWP 3671))]#0 0x00007f449d473ef3 in epoll_wait () from /lib64/libc.so.6 (gdb) bt

0 0x00007f449d473ef3 in epoll_wait () from /lib64/libc.so.6

1 0x00007f449db67326 in epoll_dispatch (base=0xea0bd0, tv=<value optimized out>) at epoll.c:407

2 0x00007f449db55ac6 in event_base_loop (base=0xea0bd0, flags=0) at event.c:1607

3 0x0000000000419934 in worker_libevent (arg=<value optimized out>) at thread.c:378

4 0x00007f449d7269d1 in start_thread () from /lib64/libpthread.so.0

5 0x00007f449d4738fd in clone () from /lib64/libc.so.6

$ ldd memcached-debug linux-vdso.so.1 => (0x00007fff655ff000) libevent-2.0.so.5 => /usr/lib64/libevent-2.0.so.5 (0x00007f7f9f193000) librt.so.1 => /lib64/librt.so.1 (0x00007f7f9ef8b000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f7f9ed6d000) libc.so.6 => /lib64/libc.so.6 (0x00007f7f9e9d9000) /lib64/ld-linux-x86-64.so.2 (0x00007f7f9f3e7000)

Comment #1

Posted on May 20, 2015 by Quick Bear

I hit the same "make test' problem on Ubuntu 14.04.2 LTS (GNU/Linux 3.13.0-48-generic x86_64) and memcached-1.4.24

t/lru-crawler.t ...... 93/221 Timeout.. killing the process t/lru-crawler.t ...... Failed 126/221 subtests

This is on an micro Amazon EC2 instance with 1GB memory.

$ ldd memcached-debug linux-vdso.so.1 => (0x00007ffff7198000) libevent-2.0.so.5 => /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 (0x00007fb17e2e4000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fb17e0c6000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fb17dd00000) /lib64/ld-linux-x86-64.so.2 (0x00007fb17e530000)

Comment #2

Posted on Jun 29, 2015 by Quick Ox

Just realized that i've opened another bug for the same issue: https://code.google.com/p/memcached/issues/detail?id=417

Comment #3

Posted on Jul 21, 2015 by Helpful Kangaroo

Comment deleted

Comment #4

Posted on Jul 22, 2015 by Swift Lion

Same problem here, Ubuntu 14.04, build (latest) from source.

t/lru-crawler.t ...... 93/221 Timeout.. killing the process t/lru-crawler.t ...... Failed 126/221 subtests

Test Summary Report

t/lru-crawler.t (Wstat: 13 Tests: 95 Failed: 0) Non-zero wait status: 13 Parse errors: Bad plan. You planned 221 tests but ran 95. Files=51, Tests=7370, 758 wallclock secs ( 2.33 usr 0.26 sys + 8.64 cusr 2.50 csys = 13.73 CPU) Result: FAIL make: * [test] Error 1

$ldd memcached-debug linux-vdso.so.1 => (0x00007fff8fffe000) libevent-2.0.so.5 => /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 (0x00007ff0270d2000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007ff026eb4000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007ff026aee000) /lib64/ld-linux-x86-64.so.2 (0x00007ff02731f000)

Comment #5

Posted on Aug 5, 2015 by Helpful Monkey

For me it only fails on One CPU instance, anything with 2 or more cpu can finish the test

Status: New

Labels:
Type-Defect Priority-Medium