Comment 2 for bug 2061913

I also counted 19 failed tests (that we know of). I don't have a solid feeling whether these are having the same root cause or could be multiple underlying issues. It would not surprise me, for example, if there are ppc64el-specific issues in valgrind itself, in addition to separate and unrelated issues in pmdk. Also, if there is one specific op code, for example, that causes all these failures, I have not had luck in pinpointing it and it feels like it might require at least a deep dive or even manual debugging on a ppc64el host. I also don't think it is wise to assume Debian or upstream is prepared and ready to do that at the moment.

Given the uncertainty + short timeframe, after a discussion the server team determined best approach would be to bypass the tests on ppc64el, to get a successful build, that will hopefully migrate and allow its rdepends to resolve.

We can't be certain whether these tests represent actual faults that will affect users, or are false positives or testsuite-specific issues that won't affect them. Just in case it's the former, this should be identified as a known issue in the release notes, a priority given to ascertain which is the case, and then the release notes updated and followup SRU bugs filed accordingly.

For now, we'll use this bug report for tracking purposes of the investigation of the test failures generally, but may wish to divide this into separate bug reports for more specific issues and use this as an umbrella bug report. I'll prioritize this as a "server-todo" bug for this work.