-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
test: disable test-crypto-secure-heap with asan #36900
test: disable test-crypto-secure-heap with asan #36900
Conversation
fast-track? |
Just waiting on the last CI run to finish then will land this... |
Landed in eef75a957c38 |
There is no commit eef75a957c38 on master.. |
The asan checks don't play well currently with persistent secure heap allocations. Signed-off-by: James M Snell <[email protected]> PR-URL: nodejs#36900 Refs: nodejs#36881 Reviewed-By: Danielle Adams <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Filip Skokan <[email protected]>
3460b40
to
6e3a832
Compare
Landed in 6e3a832 |
The asan checks don't play well currently with persistent secure heap allocations. Signed-off-by: James M Snell <[email protected]> PR-URL: #36900 Refs: #36881 Reviewed-By: Danielle Adams <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Filip Skokan <[email protected]>
Okay, but shouldn't there be at least a TODO comment for actually fixing this memory leak? It doesn't look like there's a call to |
Forgot the todo but adding the |
The asan checks don't play well currently with persistent secure
heap allocations.
Signed-off-by: James M Snell [email protected]
Refs: #36881