On 2025-02-03 6:10 a.m., Alexander Kanavin wrote: > On Fri, 31 Jan 2025 at 23:37, Richard Purdie via > lists.openembedded.org > wrote: >> Thanks Khem, this passed in testing, the only issue was valgrind ptests >> failing: >> >> https://autobuilder.yoctoproject.org/valkyrie/#/builders/61/builds/851/steps/12/logs/stdio >> https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/853/steps/12/logs/stdio >> >> Copying Randy... > Let me bite: it's time we drop valgrind ptest. Okay but I'm not going to give up on the ptests completely yet so the patch just disables ptest build, install, etc. > It's just a non stop > headache to support and I haven't once seen it provide actual value. It certainly has been a headache! I agree that most of the issues have not provided value but I think some of the target tuning likely came out of trying to run the ptests. Patch being tested: 966f4c6fc5   2025-02-03   (HEAD -> master-next) valgrind: disable ptests d392981530   2024-11-29   valgrind: update 3.23.0 -> 3.24.0 (ptest fails, vg_regtest needs rebase) glibc is ready to go to AB but I need to confirm that musl still builds. I'd prefer to keep this order even if the update breaks ptests so that if we do decide to re-enable the ptests, it's easier. ../Randy > > Alex -- # Randy MacLeod # Wind River Linux