Bug 14430

Summary: valgrind memcheck/tests/linux/stack_changes failure
Product: [QA/Testing] Package Testing (ptest) Reporter: Alexandre Belloni <alexandre.belloni>
Component: ptestAssignee: Mingli Yu <mingli.yu>
Status: NEW --- QA Contact:
Severity: normal    
Priority: Medium+ CC: randy.macleod, richard.purdie
Version: 3.4   
Target Milestone: 6.1 M2   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Comment 3 Tony Tascioglu 2021-07-23 16:17:56 UTC
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.
Comment 4 Randy MacLeod 2022-04-18 20:45:22 UTC
No news upstream. I'll check on this when I update valgrind in May.
Comment 5 Randy MacLeod 2023-02-07 19:39:26 UTC
Nothing from upstream. Move to M3.
Comment 6 Randy MacLeod 2024-03-25 23:47:56 UTC
Bulk move to 5.0-M4
Comment 7 Randy MacLeod 2024-04-25 01:26:29 UTC
Park in 5.99 until I'm sure I have time to work on an issue.
Comment 8 Randy MacLeod 2026-05-07 15:03:53 UTC
Mingli,

Can you summarize where you are with valgrind ptest and the upstream valgrind community? Are they open to working together?