Validate HTTPS scheme in LSPS5 URL Readable deserialization #22905
vincenzopalazzobuild.yml
on: pull_request
fuzz
3m 7s
Matrix: build-bindings / build
Matrix: build-cfg-flags / build
Matrix: build-features / build
Matrix: build-nostd / build
Matrix: build-sync / build
Matrix: build-workspace / build
ext-test
3m 36s
benchmark
3m 5s
check_release
3m 0s
check_docs
3m 5s
fuzz_sanity
3m 7s
linting
2m 31s
rustfmt
15s
tor-connect
3m 7s
notify-failure
Annotations
33 errors and 7 warnings
|
rustfmt
Process completed with exit code 1.
|
|
check_release
Canceling since a higher priority waiting request for Continuous Integration Checks-refs/pull/4560/merge exists
|
|
check_docs
Canceling since a higher priority waiting request for Continuous Integration Checks-refs/pull/4560/merge exists
|
|
check_docs
The operation was canceled.
|
|
build-features / build (self-hosted, 1.75.0)
Canceling since a higher priority waiting request for Continuous Integration Checks-refs/pull/4560/merge exists
|
|
build-features / build (self-hosted, 1.75.0)
The operation was canceled.
|
|
build-sync / build (self-hosted, 1.75.0)
Canceling since a higher priority waiting request for Continuous Integration Checks-refs/pull/4560/merge exists
|
|
build-sync / build (self-hosted, 1.75.0)
The operation was canceled.
|
|
build-bindings / build (self-hosted, 1.75.0)
Canceling since a higher priority waiting request for Continuous Integration Checks-refs/pull/4560/merge exists
|
|
build-bindings / build (self-hosted, 1.75.0)
The operation was canceled.
|
|
fuzz_sanity
Canceling since a higher priority waiting request for Continuous Integration Checks-refs/pull/4560/merge exists
|
|
fuzz_sanity
The operation was canceled.
|
|
benchmark
Canceling since a higher priority waiting request for Continuous Integration Checks-refs/pull/4560/merge exists
|
|
benchmark
The operation was canceled.
|
|
fuzz
Canceling since a higher priority waiting request for Continuous Integration Checks-refs/pull/4560/merge exists
|
|
fuzz
The operation was canceled.
|
|
build-workspace / build (self-hosted, 1.75.0)
Canceling since a higher priority waiting request for Continuous Integration Checks-refs/pull/4560/merge exists
|
|
build-workspace / build (self-hosted, 1.75.0)
The operation was canceled.
|
|
tor-connect
Canceling since a higher priority waiting request for Continuous Integration Checks-refs/pull/4560/merge exists
|
|
tor-connect
The operation was canceled.
|
|
build-nostd / build (self-hosted, 1.75.0)
Canceling since a higher priority waiting request for Continuous Integration Checks-refs/pull/4560/merge exists
|
|
build-nostd / build (self-hosted, 1.75.0)
The operation was canceled.
|
|
ext-test
Canceling since a higher priority waiting request for Continuous Integration Checks-refs/pull/4560/merge exists
|
|
ext-test
The operation was canceled.
|
|
build-cfg-flags / build (self-hosted, 1.75.0)
Canceling since a higher priority waiting request for Continuous Integration Checks-refs/pull/4560/merge exists
|
|
build-cfg-flags / build (self-hosted, 1.75.0)
The operation was canceled.
|
|
Continuous Integration Checks
Canceling since a higher priority waiting request for Continuous Integration Checks-refs/pull/4560/merge exists
|
|
Continuous Integration Checks
Canceling since a higher priority waiting request for Continuous Integration Checks-refs/pull/4560/merge exists
|
|
Continuous Integration Checks
Canceling since a higher priority waiting request for Continuous Integration Checks-refs/pull/4560/merge exists
|
|
Continuous Integration Checks
Canceling since a higher priority waiting request for Continuous Integration Checks-refs/pull/4560/merge exists
|
|
Continuous Integration Checks
Canceling since a higher priority waiting request for Continuous Integration Checks-refs/pull/4560/merge exists
|
|
Continuous Integration Checks
Canceling since a higher priority waiting request for Continuous Integration Checks-refs/pull/4560/merge exists
|
|
Continuous Integration Checks
Canceling since a higher priority waiting request for Continuous Integration Checks-refs/pull/4560/merge exists
|
|
rustfmt
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 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/
|
|
linting
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 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/
|
|
check_release
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 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/
|
|
benchmark
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. 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/
|
|
benchmark
Failed to restore:
|
|
benchmark
Failed to restore:
|
|
tor-connect
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 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/
|