call for testers

[Paul Querna]

FreeBSD 6.1, AMD64:
Compile warnings:
items.c: In function `item_link_q':
items.c:143: warning: comparison is always true due to limited range of
data type
items.c: In function `item_unlink_q':
items.c:161: warning: comparison is always true due to limited range of
data type

Tests:
test/00-startup.........ok

test/64bit..............
test/64bit..............NOK 2#   Failed test 'max bytes is 4097 MB'

#   in test/64bit.t at line 48.
#          got: undef
#     expected: '4296015872'

#   Failed test 'correct value'
test/64bit..............NOK 3#   in test/64bit.t at line 49.

#          got: undef
#     expected: '4294967328'

#   Failed test 'no active slabs'
test/64bit..............NOK 4#   in test/64bit.t at line 50.

#          got: undef
#     expected: '0'

And it hung at this point for a couple minutes...




Intel OSX 10.4.7:
Compile Warnings:
items.c: In function 'item_link_q':
items.c:143: warning: comparison is always true due to limited range of
data type
items.c: In function 'item_unlink_q':
items.c:161: warning: comparison is always true due to limited range of
data type

Tests:
test/00-startup.........ok

test/64bit..............ok 1/6#     Failed test (test/64bit.t at line
48)
#          got: undef
test/64bit..............NOK 2#     expected: '4296015872'

#     Failed test (test/64bit.t at line 49)
test/64bit..............NOK 3#          got: undef

#     expected: '4294967328'
#     Failed test (test/64bit.t at line 50)
test/64bit..............NOK 4#          got: undef

#     expected: '0'

It also hung at this point in the tests.

This one is weird.. Its not even a 64bit system.  Where is the decision
made that its a 64bit machine?





RHEL4 update 3, AMD64:
Compile warnings:
items.c: In function `item_link_q':
items.c:143: warning: comparison is always true due to limited range of
data type
items.c: In function `item_unlink_q':
items.c:161: warning: comparison is always true due to limited range of
data type

Test:
test/slab-reassign......skipped
        all skipped: Tests not written.
test/managed-buckets....skipped
        all skipped: Tests not written.
test/daemonize..........ok

test/delete-window......ok 18/20# waiting 5 seconds for the deleter
event...
test/delete-window......ok

test/lru................skipped
        all skipped: Tests not written.
test/flush-all..........ok

        2/11 skipped: flush_all is still only second-granularity.  need
atomic counter on flush_all.
test/flags..............ok

test/expirations........ok

test/getset.............ok

test/binary-get.........skipped
        all skipped: Tests not written.
test/unixsocket.........skipped
        all skipped: Tests not written.
test/bogus-commands.....ok

test/udp................skipped
        all skipped: Tests not written.
test/stats..............skipped
        all skipped: Tests not written.
test/00-startup.........ok

test/incrdecr...........ok

test/multiversioning....ok

test/64bit..............ok

All tests successful, 7 tests and 2 subtests skipped.
Files=18, Tests=100, 17 wallclock secs ( 0.75 cusr +  0.18 csys =  0.93 CPU)


Brad Fitzpatrick wrote:
> Before I do a release, can I get some people running the test suite on
> this snapshot?
> 
> http://danga.com/memcached/dist/experimental/memcached-1.2.x-svn357.tar.gz
> 
> Instructions:
> 
>   -- ./configure
>   -- make
>   -- prove test
>      -- if all good (you see at bottom:  "All tests successful, ...."),
>         let me know.
>      -- if bad, reply with "prove -v test", which will show verbose
>         per-test output
> 
> Looking for:
> 
>   -- Various Linux Distros (I've tried Debian and CentOS)
>   -- Solaris 10 (my Nexenta VM is failing to boot again)
>   -- FreeBSD
>   -- OS X
>   -- 64-bit whatevers (I did test it on 64-bit CentOS)
> 
> Let me know of any quirks, even if they're not part of the tests.
> 
> - Brad