linux/poky.git/meta/recipes-devtools/valgrind, branch honister

valgrind: set precise BSD license

2021-09-04T07:44:11+00:00

"BSD" is ambiguous, use the precise license BSD-3-Clause. (From OE-Core rev: b12cbda349658ddef8cb72d5738c094c2b009e7e) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

valgrind: skip broken ptests for glibc 2.34

2021-08-12T05:26:15+00:00

Skip tests that are problematic for glibc-2.34. The list of problematic ptests was found by Richard after patching several to work with the new glibc version. https://bugzilla.yoctoproject.org/show_bug.cgi?id=14500 (From OE-Core rev: c177c7f9ef6f90ca49074f003accb8e9a1a645aa) Signed-off-by: Tony Tascioglu Signed-off-by: Richard Purdie

valgrind: Add patches for glibc 2.34 support

2021-08-05T07:53:41+00:00

This partially resolves ptest failures with glibc 2.34. (From OE-Core rev: 9adf897176924cad6b12d4da73a904cfbf578f46) Signed-off-by: Richard Purdie

Convert to new override syntax

2021-08-02T14:44:10+00:00

This is the result of automated script conversion: scripts/contrib/convert-overrides.py converting the metadata to use ":" as the override character instead of "_". (From OE-Core rev: 42344347be29f0997cc2f7636d9603b1fe1875ae) Signed-off-by: Richard Purdie

valgrind: skip flaky ptest fb_test_amd64

2021-07-16T20:23:44+00:00

Recently, the none/tests/amd64/fb_test_amd64 test had been flaky and causing failures on the auto-builder. Until we can get to the root cause of the issue, we are going to skip the test to reduce the noise from the ptests. (From OE-Core rev: a365cd7a358db96791033e6dc6e45d2e816d3e4c) Signed-off-by: Tony Tascioglu Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

valgrind: Actually install list of non-deterministic ptests

2021-06-17T12:42:31+00:00

Install list of non-deterministic threaded ptests to be run using taskset to force them to a single core. This commit works with b318944d7, which updated the testing script to run the non-deterministic tests separately but didn't install the list of tests, so these tests were being run without taskset. The taskset_nondeterministic_tests file is the list of tests that will be run separately with taskset, and ignored during the other tests. This is installed to /usr/lib/valgrind/ptest similar to the 2 existing lists for tests to skip on ARM and all architectures. Removed bar_bad and bar_bad_xml to be included separately as they cause issues on non-kvm QEMU instances. See: b318944dd7 valgrind: Improve non-deterministic ptest reliability for more info. (From OE-Core rev: 3d23985d0d653844863ed513d75d93a36359992f) Signed-off-by: Tony Tascioglu Signed-off-by: Richard Purdie

valgrind: remove buggy ptest from arm64

2021-06-12T07:38:29+00:00

This commit removes the stack_changes ptest from aarch64 devices. This test is buggy and fails almost 100% of the time in qemuarm64. In general, many of the valgrind tests are more likely to fail on qemuarm64 vs native x86_64. This test previously worked on gatesgarth and dunfell, but has been failing since hardknott. It might be due to a recent change in the cross-compiler or glibc. The test runs fine when running natively on arm on a Raspberry Pi. Until we can find the root cause for the failures, this shorter term solution should clear up some of the noise from the autobuilder from a known failure. (From OE-Core rev: 82d6411b80a46d8ec0258ca75c3c80dc6128d44e) Signed-off-by: Tony Tascioglu Signed-off-by: Richard Purdie

valgrind: fix a typo

2021-06-08T11:12:40+00:00

(From OE-Core rev: 0478d9b04d6a6d10e439116b23b641a1e2553e26) Signed-off-by: Kai Kang Signed-off-by: Richard Purdie

valgrind: Improve non-deterministic ptest reliability

2021-06-06T22:16:51+00:00

Several of the valgrind tests (particulaly helgrind) are unreliable and can fail with a different output. Particularly, there is a higher chance of failure on QEMU instances with SMP enabled and on systems with more interrupts such as laptops on powersave. The tests have been reported upstream as being unreliable dating back over 5 years, due in part to the ordering of threads during an "unwinding" process in helgrind. https://bugs.kde.org/show_bug.cgi?id=345121 https://bugs.kde.org/show_bug.cgi?id=430321 A workaround to improve the reliability of such tests is to force them to run on a single CPU core using taskset. This greatly reduces the chance of a failure. >From my testing, I have found it can help reduce the rate of failures on both a laptop and QEMU by over 5x. Stress-testing in QEMU for several hours did not result in a failure while running the test normally did. The flaky or undeterministic thread-based tests are defined in the taskset_nondeterministic_tests file. These test cases will be run with taskset 0x00000001 to run on a single CPU core rather then the regular test. The edited run-ptest executes the flaky tests first, then ignores them to not duplicate the results from the main tests. Everything modified is restored when testing is complete. The drawback is that this isn't a foolproof solution. It helps the tests fail much less frequently, and considering how this issue has been documented for a long time, a workaround such as this is needed. (From OE-Core rev: b318944dd72ca7b0408e955f3599381ab3ac3ba8) Signed-off-by: Tony Tascioglu Signed-off-by: Richard Purdie

ptest: add newly discovered missing runtime dependencies across recipes

2021-05-27T12:21:38+00:00

Making ptest images based on core-image-minimal uncovered quite a few missing depenendcies from various recipes, here they are. (From OE-Core rev: 2cda6242f2f0f6f9c6bdef72bbb271eab7e5e1f5) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie