Skip to content

pmem2_map/TEST[0,1,4,5,11,12,13,14,15,16,24,25,26,27,29,30]: failed (short/release/memcheck) #5600

@szadam

Description

@szadam

ISSUE:

Environment Information

  • PMDK package version(s): 50693c2
  • OS(es) version(s): openSUSE15_3
  • ndctl version(s): 71.1
  • kernel version(s): 5.3.18-150300.59.106

Please provide a reproduction of the bug:

[pmdk_thread_1] pmem2_map/TEST0:  [91mFAILED [0m        (short/release/memcheck/byte)
[pmdk_thread_1] Valgrind log validation failed
[pmdk_thread_1] pmem2_map/TEST0: SETUP        (short/release/memcheck/page)
[pmdk_thread_1] Last 3 lines of /home/jenkins-slave/workspace/PMDK-unittests-linux-py/pmdk_1/src/test/pmem2_map/out0.log below (whole file has 3 lines):
[pmdk_thread_1] pmem2_map/TEST0: START: pmem2_map
[pmdk_thread_1]  /home/jenkins-slave/workspace/PMDK-unittests-linux-py/pmdk_1/src/test/pmem2_map/pmem2_map test_map_rdrw_file /tmp/1/pmem2_map_0/testfile
[pmdk_thread_1] pmem2_map/TEST0: DONE
[pmdk_thread_1] Last 3 lines of /home/jenkins-slave/workspace/PMDK-unittests-linux-py/pmdk_1/src/test/pmem2_map/trace0.log below (whole file has 3 lines):
[pmdk_thread_1] {pmem2_map.c:925 main} pmem2_map/TEST0: START: pmem2_map
[pmdk_thread_1]  /home/jenkins-slave/workspace/PMDK-unittests-linux-py/pmdk_1/src/test/pmem2_map/pmem2_map test_map_rdrw_file /tmp/1/pmem2_map_0/testfile
[pmdk_thread_1] {pmem2_map.c:927 main} pmem2_map/TEST0: DONE
[pmdk_thread_1] Last 30 lines of /home/jenkins-slave/workspace/PMDK-unittests-linux-py/pmdk_1/src/test/pmem2_map/memcheck0.log below (whole file has 30 lines):
[pmdk_thread_1] ==42155== Memcheck, a memory error detector
[pmdk_thread_1] ==42155== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
[pmdk_thread_1] ==42155== Using Valgrind-3.20.0 and LibVEX; rerun with -h for copyright info
[pmdk_thread_1] ==42155== Command: /home/jenkins-slave/workspace/PMDK-unittests-linux-py/pmdk_1/src/test/pmem2_map/pmem2_map test_map_rdrw_file /tmp/1/pmem2_map_0/testfile
[pmdk_thread_1] ==42155== Parent PID: 60875
[pmdk_thread_1] ==42155== 
[pmdk_thread_1] ==42155== 
[pmdk_thread_1] ==42155== HEAP SUMMARY:
[pmdk_thread_1] ==42155==     in use at exit: 256 bytes in 4 blocks
[pmdk_thread_1] ==42155==   total heap usage: 4,602 allocs, 4,598 frees, 6,437,045 bytes allocated
[pmdk_thread_1] ==42155== 
[pmdk_thread_1] ==42155== 144 (64 direct, 80 indirect) bytes in 1 blocks are definitely lost in loss record 4 of 4
[pmdk_thread_1] ==42155==    at 0x4C32735: malloc (vg_replace_malloc.c:393)
[pmdk_thread_1] ==42155==    by 0x455484: _Malloc (alloc.c:72)
[pmdk_thread_1] ==42155==    by 0x410997: pmem2_malloc (pmem2_utils.c:21)
[pmdk_thread_1] ==42155==    by 0x40A8A4: mover_new (mover.c:183)
[pmdk_thread_1] ==42155==    by 0x40DED2: pmem2_map_new (map_posix.c:523)
[pmdk_thread_1] ==42155==    by 0x404F63: test_map_rdrw_file (pmem2_map.c:170)
[pmdk_thread_1] ==42155==    by 0x404AA4: TEST_CASE_PROCESS (unittest.h:700)
[pmdk_thread_1] ==42155==    by 0x406FFC: main (pmem2_map.c:926)
[pmdk_thread_1] ==42155== 
[pmdk_thread_1] ==42155== LEAK SUMMARY:
[pmdk_thread_1] ==42155==    definitely lost: 64 bytes in 1 blocks
[pmdk_thread_1] ==42155==    indirectly lost: 80 bytes in 1 blocks
[pmdk_thread_1] ==42155==      possibly lost: 0 bytes in 0 blocks
[pmdk_thread_1] ==42155==    still reachable: 0 bytes in 0 blocks
[pmdk_thread_1] ==42155==         suppressed: 112 bytes in 2 blocks
[pmdk_thread_1] ==42155== 
[pmdk_thread_1] ==42155== For lists of detected and suppressed errors, rerun with: -s
[pmdk_thread_1] ==42155== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

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

always

Actual behavior:

Tests failed.

Expected behavior:

Tests should pass.

Metadata

Metadata

Assignees

No one assigned

    Labels

    CI: DisabledTemporarily disabled from testingQA: CI.github/ and utils/ related to automated testingType: BugA previously unknown bug in PMDKlibpmem2libpmem- and libpmem2-relatedminiasyncasync related issue

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions