pmem / issues

Old issues repo for PMDK.
http://pmem.io
13 stars 7 forks source link

Test: pmemobjcli/TEST1: SETUP (all/pmem/debug/memcheck) fails #1111

Closed Greg091 closed 5 years ago

Greg091 commented 5 years ago

ISSUE:

Environment Information

Please provide a reproduction of the bug:

./RUNTESTS pmemobjcli -s TEST1 -m force-enable -t all

How often bug is revealed: (always, often, rare): always

Actual behavior:

./RUNTESTS pmemobjcli -s TEST1 -m force-enable -t all
pmemobjcli/TEST1: SETUP (all/pmem/debug/memcheck)
pmemobjcli/TEST1 failed with Valgrind. See memcheck1.log. First 20 lines below.
pmemobjcli/TEST1 memcheck1.log ==15077==     in use at exit: 24 bytes in 1 blocks
pmemobjcli/TEST1 memcheck1.log ==15077==   total heap usage: 21,372 allocs, 21,364 frees, 14,207,827 bytes allocated
pmemobjcli/TEST1 memcheck1.log ==15077== 
pmemobjcli/TEST1 memcheck1.log ==15077== 24 bytes in 1 blocks are definitely lost in loss record 1 of 1
pmemobjcli/TEST1 memcheck1.log ==15077==    at 0x4C2BFE8: realloc (vg_replace_malloc.c:785)
pmemobjcli/TEST1 memcheck1.log ==15077==    by 0x40541B: pocli_args_alloc (in /home/jenkins/workspace/1.6.1/1.4.3/memcheck_143/src/test/tools/pmemobjcli/pmemobjcli)
pmemobjcli/TEST1 memcheck1.log ==15077==    by 0x408AFA: pocli_process (in /home/jenkins/workspace/1.6.1/1.4.3/memcheck_143/src/test/tools/pmemobjcli/pmemobjcli)
pmemobjcli/TEST1 memcheck1.log ==15077==    by 0x408D21: pocli_pmemobj_tx_begin (in /home/jenkins/workspace/1.6.1/1.4.3/memcheck_143/src/test/tools/pmemobjcli/pmemobjcli)
pmemobjcli/TEST1 memcheck1.log ==15077==    by 0x408B0C: pocli_process (in /home/jenkins/workspace/1.6.1/1.4.3/memcheck_143/src/test/tools/pmemobjcli/pmemobjcli)
pmemobjcli/TEST1 memcheck1.log ==15077==    by 0x404F43: main (in /home/jenkins/workspace/1.6.1/1.4.3/memcheck_143/src/test/tools/pmemobjcli/pmemobjcli)
pmemobjcli/TEST1 memcheck1.log ==15077== 
pmemobjcli/TEST1 memcheck1.log ==15077== LEAK SUMMARY:
pmemobjcli/TEST1 memcheck1.log ==15077==    definitely lost: 24 bytes in 1 blocks
pmemobjcli/TEST1 memcheck1.log ==15077==    indirectly lost: 0 bytes in 0 blocks
pmemobjcli/TEST1 memcheck1.log ==15077==      possibly lost: 0 bytes in 0 blocks
pmemobjcli/TEST1 memcheck1.log ==15077==    still reachable: 0 bytes in 0 blocks
pmemobjcli/TEST1 memcheck1.log ==15077==         suppressed: 0 bytes in 0 blocks
pmemobjcli/TEST1 memcheck1.log ==15077== 
pmemobjcli/TEST1 memcheck1.log ==15077== For counts of detected and suppressed errors, rerun with: -v
pmemobjcli/TEST1 memcheck1.log ==15077== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
RUNTESTS: stopping: pmemobjcli/TEST1 failed, TEST=all FS=pmem BUILD=debug

Expected behavior:

Test should pass.

Details

Additional information about Priority and Help Requested:

Are you willing to submit a pull request with a proposed change? (Yes, No)

Requested priority: (Showstopper, High, Medium, Low)

marcinslusarz commented 5 years ago

Ref: #930

Fixing this in stable-1.4 may introduce regressions outside of this (testing) tool. Closing.