AB Image Link: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.0.rc1/ptest/machines/genericx86-64/core-image-sato-sdk-genericx86-64.hddimg pTest valgrind report: https://wiki.yoctoproject.org/wiki/Ptest_eac61f37e36099f74485dab398b57f3812826d17 poky: eac61f37e36099f74485dab398b57f3812826d17 HW Tested: NUC D54250WYK Results for NUC ptest valgrind 2015-10-02: ******************************** Tests that failed now and worked last time: 4 memcheck/tests/leak_cpp_interior massif/tests/overloaded-new drd/tests/pth_barrier_thr_cr massif/tests/new-cpp
In the latest image, i found that did not have Ptest files in valgrind which path is /usr/lib.
Maxin, can you see what the state of valgrind ptest for 2.1 is and see if we need to sort this in master?
(In reply to comment #2) > Maxin, can you see what the state of valgrind ptest for 2.1 is and see if we > need to sort this in master I will look into that. Thanks
WIth the current master, valgrind ptests are present in the expected path: # /usr/lib/valgrind/ptest However, a large number of ptests fails to run (here: qemumips) and some tests get terminated by OOM killer. root@qemumips:/usr/lib/valgrind/ptest# ./run-ptest FAIL: cachegrind/tests/chdir FAIL: cachegrind/tests/clreq FAIL: cachegrind/tests/dlclose FAIL: cachegrind/tests/notpower2 FAIL: cachegrind/tests/wrap5 FAIL: callgrind/tests/clreq FAIL: callgrind/tests/notpower2-hwpref FAIL: callgrind/tests/notpower2-use FAIL: callgrind/tests/notpower2-wb FAIL: callgrind/tests/notpower2 FAIL: callgrind/tests/simwork-both FAIL: callgrind/tests/simwork-branch FAIL: callgrind/tests/simwork-cache FAIL: callgrind/tests/simwork1 FAIL: callgrind/tests/simwork2 FAIL: callgrind/tests/simwork3 timed out FAIL: callgrind/tests/threads-use FAIL: callgrind/tests/threads timed out FAIL: drd/tests/annotate_barrier timed out FAIL: drd/tests/annotate_barrier_xml timed out FAIL: drd/tests/annotate_hb_err FAIL: drd/tests/annotate_hb_race timed out drd-mips32-linu invoked oom-killer: gfp_mask=0x24201ca, order=0, oom_score_adj=0 drd-mips32-linu cpuset=/ mems_allowed=0 CPU: 0 PID: 1410 Comm: drd-mips32-linu Not tainted 4.4.3-yocto-standard #1 Stack : 0000004a 00000000 00000000 00000000 8016cb44 809c64a4 809beb8c 00000582 80b43708 809d084c 00004003 8df47ccc 80a55fb0 8016cb74 80a55fb0 8051e358 80b476f0 00000000 809c64a4 8dd19b2c 8df683c0 80201a64 0000f209 8012ada4 00000000 809d084c 8dd19b2c 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 ... Call Trace: [<8010c8e4>] show_stack+0xe4/0x100 [<80264ee8>] dump_header.isra.6+0x68/0x1f8 [<80207f78>] oom_kill_process+0x320/0x544 [<80208558>] out_of_memory+0x388/0x3cc [<8020d9ac>] __alloc_pages_nodemask+0xaa0/0xad0 [<802063d4>] filemap_fault+0x228/0x5e4 [<80236048>] __do_fault+0x38/0xa4 [<8023a68c>] handle_mm_fault+0x950/0x1474 [<80878758>] __do_page_fault+0x1bc/0x63c [<80105f84>] resume_userspace_check+0x0/0x10 Mem-Info: active_anon:56780 inactive_anon:191 isolated_anon:0 active_file:16 inactive_file:68 isolated_file:0 unevictable:0 dirty:0 writeback:0 unstable:0 slab_reclaimable:1243 slab_unreclaimable:1666 mapped:179 shmem:226 pagetables:291 bounce:0 free:729 free_pcp:16 free_cma:0 ... ... Out of memory: Kill process 2059 (drd-mips32-linu) score 259 or sacrifice child Killed process 2059 (drd-mips32-linu) total-vm:87648kB, anon-rss:66232kB, file-rss:4kB
Commit: 6e20b31d5d17133e0fca086e12a0ad06ab5c4cc8 Image: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.3_M3.rc1/machines/genericx86-64/core-image-sato-sdk-ptest-genericx86-64.hddimg HW: NUC6 All test case are failing for 2.3 M3 rc1
Fixed in master: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=867c2dcbd76b7cfadf03e5237b19d5cbd892dd0d
Created attachment 3830 [details] ptest_full log
commit:poky : 6964efddd31c479386d1643c1025bc102710392f Image: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.4_M1.rc1/machines/genericx86-64/core-image-sato-sdk-ptest-genericx86-64.hddimg HW: NUC 6i5SYH some test case are failing for 2.4_M1.rc1 full log in attachment
Valgrind ptests are not reliable currently. *** This bug has been marked as a duplicate of bug 12837 ***