-
Notifications
You must be signed in to change notification settings - Fork 304
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DAOS-16238 utils: Add valgrind suppressions for Go runtime #14823
Conversation
Added some more Go runtime suppressions. I've added counterparts for all functions already on the list, as well as the false positives that have been recently spotted. Required-githooks: true Signed-off-by: Kris Jacque <kris.jacque@intel.com>
Ticket title is 'Sporadic invalid read/write NLT issues in master PRs' |
No Features tag needed, as this affects only NLT. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🫡 LGTM
Test stage Functional Hardware Medium Verbs Provider completed with status UNSTABLE. https://build.hpdd.intel.com/job/daos-stack/job/daos//view/change-requests/job/PR-14823/1/testReport/ |
NLT has passed. This patch only affects the valgrind suppressions. It could not have affected the hardware tests. |
Added some more Go runtime suppressions. I've added counterparts for all functions already on the list, as well as the false positives that have been recently spotted. Required-githooks: true Signed-off-by: Kris Jacque <kris.jacque@intel.com>
…14863) Added some more Go runtime suppressions. I've added counterparts for all functions already on the list, as well as the false positives that have been recently spotted. Signed-off-by: Kris Jacque <kris.jacque@intel.com>
Added some more Go runtime suppressions. I've added counterparts for all functions already on the list, as well as the false positives that have been recently spotted.
Required-githooks: true
Before requesting gatekeeper:
Features:
(orTest-tag*
) commit pragma was used or there is a reason documented that there are no appropriate tags for this PR.Gatekeeper: