summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/valgrind/valgrind/run-ptest
Commit message (Collapse)AuthorAgeFilesLines
* valgrind: Remove reference to non-existent ptestsYi Fan Yu2021-02-191-1/+1
| | | | | | | | | | | | | exp-dhat: commit 441bfc5f5 promoted exp-dhat to dhat exp-sgcheck: commit 40187fcd6 removed the exp-sgcheck tool. (From OE-Core rev: f7b32e0d5bb9c80f6b37ed8b7f0bd29c562d3f70) Signed-off-by: Yi Fan Yu <yifan.yu@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* valgrind: exclude bar_bad/bar_bad_xml from ptestsAlexander Kanavin2020-12-181-0/+10
| | | | | | | | | | | | | | The tests' output is non-deterministic and sometimes doesn't match the sample output. This has been reported at https://bugs.kde.org/show_bug.cgi?id=430321 (see also an earlier related bug https://bugs.kde.org/show_bug.cgi?id=358213) Until upstream figures out how to fix this, let's not run the tests. (From OE-Core rev: 7f7d2fa18267090891754d976cbc3e628324d3dd) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* valgrind: disable 256 ptests for aarch64Randy MacLeod2019-09-161-0/+16
| | | | | | | | | | | | | | | | | | | | | | | | | On qemuarm64 systems, about half of the valgrind tests fail and often result in defunct processes, eg: root 819 818 25 00:12 pts/0 00:01:52 /usr/bin/valgrind --command-line-only=yes --memcheck:leak-check=no --tool=memcheck -q --track-origins= root 861 420 0 00:13 pts/0 00:00:00 [sh] <defunct> Eventually these processes use so much memory that the out of memory killer runs. Hide the tests that fail as a horrid work-around until the root cause has been resolved since this at least allows the ptest run to complete. This work-around is done in the run-ptest script using a sorted list of tests so that they can be easily restored one by one without a rebuild during testing. With core-image-minimal on qemuarm64: Recipe | Passed | Failed | Skipped | Time(s) valgrind | 333 | 49 | 17 | 7637 (From OE-Core rev: 208023f8fcbf4aee34544a80f962ae25f25ffb8d) Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* valgrind: ptest improvements to run-ptest and moreRandy MacLeod2019-09-161-5/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Make some changes to the run-ptest script: - after main tests run integrity check like the pkg Makefile. - aesthetic and ordering changes Add the .in_place directory and its contents which allows valgrind to be run in-place thereby enabling the gdbserver_tests to complete rather than hang. Unfortunately directory paths embedded in binaries still cause many of these test to fail. Add the exp-sgcheck tests. With core-image-minimal on qemux86-64/kvm: Recipe | Passed | Failed | Skipped | Time(s) before | 648 | 12 | 60 | 1541 after | 662 | 20 | 38 | 1429 ppc-no-gdbserv | 415 | 196 | 34 | 10689 Since fewer tests timeout, the overall time has decreased. With core-image-sato on qemux86-64/kvm the results are now the same as core-image-minimal. qemuppc/arm64 runs result in the oom-killer eventually running since some processes do not terminate properly and accumulate as defunct processes in memory. Without the gdbserver_tests, the tests complete without defunct process or the oom-killer running for ppc but not for arm64. (From OE-Core rev: 6dbaaeec17eae8329031188b688b33306a871870) Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* valgrind: improvements for run-ptestJackie Huang2017-08-231-3/+16
| | | | | | | | | | * Add statistic summary for run-ptest * Ensure the script can be run anywhere (From OE-Core rev: 8a6f5a2bc55975f38ad285ddea7122643b303c53) Signed-off-by: Jackie Huang <jackie.huang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* valgrind/oprofile/systemd: no bashism in run-ptestRobert Yang2014-08-281-1/+2
| | | | | | | | | | There is no bashism in the scripts, so use /bin/sh, and add /bin/sh interpreter for systemd's run-ptest. (From OE-Core rev: 62d455f89fb1d2c22cf987bdbb56a55e6d031ce0) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* valgrind: integration of regression tests to ptestDave Lerner2014-02-211-0/+11
Modifies valgrind's regression test framework to be compatible with the yocto PTEST framework as follows: * existing recipe valgrind*bb adds new methods: do_compile_ptest and do_install_ptest. * new file run-ptest adds the wrapper interface to the valgrind regression test script vg_regtest. * existing valgrind regression test script 'vg_regtest' changes to report the status of the valgrind component tests in the format that PTEST expects, instead of the valgrind formats, but only when vg_regtest is invoked with an optional --yocto-ptest argument * four new patches disable building tests that don't compile with the yocto compiler and default options. See the patches for details. (From OE-Core rev: d4438e421f448cdb7e25c038d657bbebc1b6486e) Signed-off-by: Dave Lerner <dave.lerner@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>