Skip to content

refs #12442 - generate a fuzzing corpus by extracting code from testrunner #17133

refs #12442 - generate a fuzzing corpus by extracting code from testrunner

refs #12442 - generate a fuzzing corpus by extracting code from testrunner #17133

Triggered via pull request May 17, 2026 19:51
Status Success
Total duration 18m 39s
Artifacts 2

selfcheck.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

1 warning
build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4, hendrikmuhs/ccache-action@v1.2. 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/

Artifacts

Produced during runtime
Name Size Digest
Callgrind Output
784 KB
sha256:cd7e8610537c08a05a817572d37b02d5f628528892c36c6c846f4fc5a8fd662e
Memcheck Output
704 Bytes
sha256:7471a00f17b5d81be4af179c49ae86339e60102908fbbf689f7aa45d8f8c8959