Skip to content

crypto: add memory tracking for secureContext openssl objects #32891

crypto: add memory tracking for secureContext openssl objects

crypto: add memory tracking for secureContext openssl objects #32891

Triggered via push April 9, 2026 04:24
Status Success
Total duration 1h 14m 21s
Artifacts
coverage-linux-without-intl
1h 14m
coverage-linux-without-intl
Fit to window
Zoom out
Zoom in

Annotations

1 warning and 1 notice
coverage-linux-without-intl
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Mozilla-Actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
sccache stats
63% - 2631 hits, 1550 misses, 0 errors