Split out of #14294 'valgrind': ['memcheck/tests/linux/stack_changes'] Seems to happen only on qemuarm64-ptest on the arm workers: https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/1840/steps/12/logs/stdio https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/1843/steps/12/logs/stdio https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/1853/steps/12/logs/stdio https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/1852/steps/12/logs/stdio https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/1850/steps/12/logs/stdio https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/1871/steps/12/logs/stdio https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/1872/steps/12/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/1884/steps/12/logs/stdio https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/1880/steps/12/logs/stdio https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/1878/steps/12/logs/stdio https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/1877/steps/12/logs/stdio https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/1876/steps/12/logs/stdio https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/1874/steps/12/logs/stdio https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/1869/steps/12/logs/stdio
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=a71c3b390dc5d1de9047bbea8557f8939a7a8141 removes the test for now
This has been reported upstream in the following bug: https://bugs.kde.org/show_bug.cgi?id=439082 This ptest only fails on ARM targets, where it fails consistently. We have skipped the ptest with the following commit http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=a71c3b390dc5d1de9047bbea8557f8939a7a8141 We're waiting on upstream to continue.
No news upstream. I'll check on this when I update valgrind in May.
Nothing from upstream. Move to M3.
Bulk move to 5.0-M4
Park in 5.99 until I'm sure I have time to work on an issue.
Mingli, Can you summarize where you are with valgrind ptest and the upstream valgrind community? Are they open to working together?