DAOS-19035 test: Genericize Cgo suppressions (#18408)

[tanabarr]

• Update Cgo suppressions with wildcards for the hashes, which can change.

Steps for the author:

• Commit message follows the guidelines.
• Appropriate Features or Test-tag pragmas were used.
• Appropriate Functional Test Stages were run.
• At least two positive code reviews including at least one code owner from each category referenced in the PR.
• Testing is complete. If necessary, forced-landing label added and a reason added in a comment.

After all prior steps are complete:

• Gatekeeper requested (daos-gatekeeper added as a reviewer).

[github-actions]

Ticket title is 'NLT - Valgrind Memcheck error detected'
Status is 'Awaiting backport'
Job should run at elevated priority (1)
https://daosio.atlassian.net/browse/DAOS-19035

[daosbuild3]

Test stage NLT completed with status UNSTABLE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net/job/daos-stack/job/daos//view/change-requests/job/PR-18435/1/testReport/

[kjacque]

Looks like a clean cherry-pick. Thanks for backporting.

[kjacque]

The NLT failure in CI looks like a different issue:

{
   <insert_a_suppression_name_here>
   Memcheck:Param
   write(buf)
   fun:internal/runtime/syscall/linux.Syscall6
}

[daosbuild3]

Test stage Functional Hardware Medium MD on SSD completed with status UNSTABLE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net/job/daos-stack/job/daos//view/change-requests/job/PR-18435/1/testReport/

[daosbuild3]

Test stage NLT completed with status UNSTABLE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net/job/daos-stack/job/daos//view/change-requests/job/PR-18435/2/testReport/

[kjacque]

Not that this hurts anything, but the file used by NLT is the cart one. Looks like the latest run had related memcheck issues, including the read variant of this. I think we should land this backport, and address the other issues in another ticket on master, which is also almost certainly affected.

I created one here: https://daosio.atlassian.net/browse/DAOS-19084

[tanabarr]

I've requested gatekeeper and forced landing because whilst it still fails NLT it fixes a number of issues, another patch will address more of the suppressions needed.

[daltonbohning]

I've requested gatekeeper and forced landing because whilst it still fails NLT it fixes a number of issues, another patch will address more of the suppressions needed.

Which other patch?

[daltonbohning]

I've requested gatekeeper and forced landing because whilst it still fails NLT it fixes a number of issues, another patch will address more of the suppressions needed.

Which other patch?

Looks like
https://daosio.atlassian.net/browse/DAOS-19084
#18448

[kjacque]

I've requested gatekeeper and forced landing because whilst it still fails NLT it fixes a number of issues, another patch will address more of the suppressions needed.

Which other patch?

Looks like https://daosio.atlassian.net/browse/DAOS-19084 #18448

Yes, this is the other patch. Different set of suppressions that are also missing on master.

[daosbuild3]

Test stage Functional Hardware Medium MD on SSD completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net//job/daos-stack/job/daos/view/change-requests/job/PR-18435/2/execution/node/1347/log

[tanabarr]

this can be landed because it only affects NLT so doesn't need to finish hardware