Show memory leak summary when valgrind check fails

[sshedi]

No description provided.

[sshedi]

error: unshare with flags x40020000 failed: Operation not permitted
error: Plugin unshare: hook scriplet_fork_post failed
warning: %post(git-2.43.7-2.ph5.x86_64) scriptlet failed, exit status 126
package git-2.43.7-2.ph5.x86_64: script warning in %postin
Error(1525) : rpm transaction failed
Error: Process completed with exit code 245.

There is a fix in progress for this.

[oliverkurth]

Thank you for this. But how does this fix the valgrind issue? I understand we'll see the error output, but why is it not failing any more?

[sshedi]

Thank you for this. But how does this fix the valgrind issue? I understand we'll see the error output, but why is it not failing any more?

Fixed it. The error was not captured because I removed exit on first error.

[oliverkurth]

error: unshare with flags x40020000 failed: Operation not permitted
error: Plugin unshare: hook scriplet_fork_post failed
warning: %post(git-2.43.7-2.ph5.x86_64) scriptlet failed, exit status 126
package git-2.43.7-2.ph5.x86_64: script warning in %postin
Error(1525) : rpm transaction failed
Error: Process completed with exit code 245.

There is a fix in progress for this.

I am trying to fix a similar issue here: vmware/photon-os-installer#41

[sshedi]

error: unshare with flags x40020000 failed: Operation not permitted
error: Plugin unshare: hook scriplet_fork_post failed
warning: %post(git-2.43.7-2.ph5.x86_64) scriptlet failed, exit status 126
package git-2.43.7-2.ph5.x86_64: script warning in %postin
Error(1525) : rpm transaction failed
Error: Process completed with exit code 245.

There is a fix in progress for this.

I am trying to fix a similar issue here: vmware/photon-os-installer#41

This is also the right thing to do, at some point we will have to align with rpm upstream and consider scriptlet errors as fatal. rpm-6.0.1-3 is published, please rebase #569

[sshedi]

The intention behind this PR is, if we are force merging a PR ignoring memory leaks; we can have a look at the leak summary and decide if it indeed from tdnf or from third party library.