Skip to content

feat: use the nss-rs blapi feature #11143

feat: use the nss-rs blapi feature

feat: use the nss-rs blapi feature #11143

Triggered via pull request May 11, 2026 06:52
Status Failure
Total duration 7m 9s
Artifacts

check.yml

on: pull_request
Determine toolchains
5s
Determine toolchains
Ensure `Cargo.lock` contains all required dependencies
21s
Ensure `Cargo.lock` contains all required dependencies
Matrix: Check Android
Matrix: Run checks for VM-only platforms
Matrix: Run checks
Fit to window
Zoom out
Zoom in

Annotations

22 errors, 23 warnings, and 4 notices
Run checks (ubuntu-24.04, 1.90.0, debug)
Process completed with exit code 101.
Run checks (ubuntu-24.04, stable, release)
Process completed with exit code 101.
Run checks (ubuntu-24.04, nightly, debug)
Process completed with exit code 101.
Run checks (macos-15, nightly, debug)
Process completed with exit code 101.
Run checks (macos-14, stable, debug)
Process completed with exit code 101.
Run checks (macos-15, stable, release)
Process completed with exit code 101.
Run checks (macos-15, stable, debug)
Process completed with exit code 101.
Run checks (macos-15, 1.90.0, debug)
Process completed with exit code 101.
Run checks (ubuntu-24.04-arm, 1.90.0, debug)
Process completed with exit code 101.
Run checks (ubuntu-24.04-arm, stable, debug)
Process completed with exit code 101.
Run checks (ubuntu-22.04, stable, debug)
Process completed with exit code 101.
Run checks (ubuntu-24.04, stable, debug)
Process completed with exit code 101.
Run checks (ubuntu-24.04-arm, nightly, debug)
Process completed with exit code 101.
Run checks for VM-only platforms (freebsd)
The process '/usr/bin/ssh' failed with exit code 101
Check Android (x86_64-linux-android)
Process completed with exit code 101.
Check Android (aarch64-linux-android)
The strategy configuration was canceled because "check-android.x86_64-linux-android" failed
Check Android (aarch64-linux-android)
The operation was canceled.
Run checks (windows-2025, stable, release)
Process completed with exit code 101.
Run checks (windows-2022, stable, debug)
Process completed with exit code 101.
Run checks (windows-2025, nightly, debug)
Process completed with exit code 101.
Run checks (windows-2025, stable, debug)
Process completed with exit code 101.
Run checks (windows-2025, 1.90.0, debug)
Process completed with exit code 101.
Run checks (ubuntu-24.04, 1.90.0, debug)
No files were found with the provided path: simulation-seeds. No artifacts will be uploaded.
Run checks (ubuntu-24.04, stable, release)
No files were found with the provided path: simulation-seeds. No artifacts will be uploaded.
Run checks (ubuntu-24.04, nightly, debug)
No files were found with the provided path: simulation-seeds. No artifacts will be uploaded.
Run checks (macos-15, nightly, debug)
No files were found with the provided path: simulation-seeds. No artifacts will be uploaded.
Run checks (macos-14, stable, debug)
No files were found with the provided path: simulation-seeds. No artifacts will be uploaded.
Run checks (macos-15, stable, release)
No files were found with the provided path: simulation-seeds. No artifacts will be uploaded.
Run checks (macos-15, stable, debug)
No files were found with the provided path: simulation-seeds. No artifacts will be uploaded.
Run checks (macos-15, 1.90.0, debug)
No files were found with the provided path: simulation-seeds. No artifacts will be uploaded.
Run checks (ubuntu-24.04-arm, 1.90.0, debug)
No files were found with the provided path: simulation-seeds. No artifacts will be uploaded.
Run checks (ubuntu-24.04-arm, stable, debug)
No files were found with the provided path: simulation-seeds. No artifacts will be uploaded.
Run checks (ubuntu-22.04, stable, debug)
No files were found with the provided path: simulation-seeds. No artifacts will be uploaded.
Run checks (ubuntu-24.04, stable, debug)
No files were found with the provided path: simulation-seeds. No artifacts will be uploaded.
Run checks (ubuntu-24.04-arm, nightly, debug)
No files were found with the provided path: simulation-seeds. No artifacts will be uploaded.
Run checks (windows-2025, stable, release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@v1. 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/
Run checks (windows-2025, stable, release)
No files were found with the provided path: simulation-seeds. No artifacts will be uploaded.
Run checks (windows-2022, stable, debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@v1. 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/
Run checks (windows-2022, stable, debug)
No files were found with the provided path: simulation-seeds. No artifacts will be uploaded.
Run checks (windows-2025, nightly, debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@v1. 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/
Run checks (windows-2025, nightly, debug)
No files were found with the provided path: simulation-seeds. No artifacts will be uploaded.
Run checks (windows-2025, stable, debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@v1. 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/
Run checks (windows-2025, stable, debug)
No files were found with the provided path: simulation-seeds. No artifacts will be uploaded.
Run checks (windows-2025, 1.90.0, debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@v1. 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/
Run checks (windows-2025, 1.90.0, debug)
No files were found with the provided path: simulation-seeds. No artifacts will be uploaded.
Run checks (windows-2025, stable, release)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
Run checks (windows-2025, nightly, debug)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
Run checks (windows-2025, stable, debug)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
Run checks (windows-2025, 1.90.0, debug)
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026