Skip to content

BoringSSL: Test key import in EVPTest a bit more extensively (#3058) #10200

BoringSSL: Test key import in EVPTest a bit more extensively (#3058)

BoringSSL: Test key import in EVPTest a bit more extensively (#3058) #10200

Triggered via push May 8, 2026 20:18
Status Cancelled
Total duration 4h 7m 16s
Artifacts

actions-ci.yml

on: push
sanity-test-run
9m 0s
sanity-test-run
Matrix: alpine-linux-x86
Matrix: arm-clang-2004-tests
Matrix: arm-clang-2204-tests
Matrix: arm-clang-2404-tests
Matrix: arm-clang-2504-tests
Matrix: arm-gcc-tests
Matrix: compiler-tests
Matrix: freebsd
Matrix: gcc-14-hardened
Matrix: macOS-ARM-FIPS
Matrix: macOS-ARM
Matrix: macOS-x86-FIPS
Matrix: macOS-x86
Matrix: musl-tests
Matrix: netbsd
Matrix: OpenBSD
Matrix: pedantic-tests
Matrix: sanitizer-tests
Matrix: windows
Fit to window
Zoom out
Zoom in

Annotations

7 errors, 15 warnings, and 1 notice
windows (windows-11-arm)
Process completed with exit code 1.
macOS-ARM-FIPS (macos-14, 20)
Process completed with exit code 1.
OpenBSD 7.6 (arm64) test
Canceling since a higher priority waiting request for General CI Tests-main exists
OpenBSD 7.6 (arm64) test
The operation was canceled.
OpenBSD 7.5 (arm64) test
Canceling since a higher priority waiting request for General CI Tests-main exists
OpenBSD 7.5 (arm64) test
The operation was canceled.
General CI Tests
Canceling since a higher priority waiting request for General CI Tests-main exists
gcc-14-hardened (14, 1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: threeal/cmake-action@v2.1.0. 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/
gcc-14-hardened (14, 0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: threeal/cmake-action@v2.1.0. 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/
NetBSD 10.1 (x86-64) test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: cross-platform-actions/action@2d97d42e1972a17b045fd709a422f7e55a86230d. 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/
FreeBSD 14.2 (x86-64) test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: cross-platform-actions/action@v0.32.0. 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/
FreeBSD 15.0 (x86-64) test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: cross-platform-actions/action@v0.32.0. 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/
OpenBSD 7.6 (x86-64) test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: cross-platform-actions/action@2d97d42e1972a17b045fd709a422f7e55a86230d. 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/
OpenBSD 7.5 (x86-64) test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: cross-platform-actions/action@2d97d42e1972a17b045fd709a422f7e55a86230d. 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/
windows (windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/setup-nasm@v1.5.1. 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/
macOS-ARM-FIPS (macos-15, 20)
llvm@20 was installed but not linked because llvm@18 is already installed. To link this version, run: brew link llvm@20
macOS-ARM-FIPS (macos-14, 20)
llvm@20 was installed but not linked because llvm@15 is already installed. To link this version, run: brew link llvm@20
NetBSD 10.1 (arm64) test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: cross-platform-actions/action@2d97d42e1972a17b045fd709a422f7e55a86230d. 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/
FreeBSD 14.2 (arm64) test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: cross-platform-actions/action@v0.32.0. 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/
FreeBSD 15.0 (arm64) test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: cross-platform-actions/action@v0.32.0. 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/
OpenBSD 7.6 (arm64) test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: cross-platform-actions/action@2d97d42e1972a17b045fd709a422f7e55a86230d. 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/
OpenBSD 7.5 (arm64) test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: cross-platform-actions/action@2d97d42e1972a17b045fd709a422f7e55a86230d. 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/
windows (windows-latest)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026