[SLG-0004]: metadata value attributes (revision 2 aka CustomStringConvertible)
#371
kukushechkinpull_request.yml
on: pull_request
Android Swift SDK
/
Construct Android Swift SDK matrix
3s
Cxx interop
/
Construct Cxx interop matrix
4s
macOS benchmarks (NoTraits)
/
Construct macOS Benchmarks matrix
5s
macOS tests
/
Construct Darwin matrix
6s
Release builds
/
Construct release build matrix
4s
Static Linux Swift SDK
/
Construct Static SDK matrix
3s
Unit tests
/
Construct unit test matrix
6s
Wasm Swift SDK
/
Construct WebAssembly Swift SDK matrix
3s
Soundness
/
API breakage check
44s
Soundness
/
Documentation check
1m 7s
Soundness
/
Documentation check (macOS)
0s
Soundness
/
Unacceptable language check
6s
Soundness
/
License headers check
5s
Soundness
/
Broken symlinks check
6s
Soundness
/
Format check
33s
Soundness
/
Shell check
30s
Soundness
/
YAML lint check
6s
Soundness
/
Python lint check
8s
Matrix: Android Swift SDK / Android Swift SDK / execute-matrix
Matrix: Cxx interop / Cxx interop / execute-matrix
Matrix: macOS benchmarks (NoTraits) / benchmarks-macos
Matrix: macOS tests / darwin-job
Matrix: Release builds / Release builds / execute-matrix
Matrix: Static Linux Swift SDK / Static SDK / execute-matrix
Matrix: Unit tests / Unit tests / execute-matrix
Matrix: Wasm Swift SDK / WebAssembly Swift SDK / execute-matrix
macOS benchmarks (MaxLogLevelWarning)
/
Construct macOS Benchmarks matrix
Matrix: macOS benchmarks (MaxLogLevelWarning) / benchmarks-macos
Waiting for pending jobs
Annotations
34 errors and 9 warnings
|
Wasm Swift SDK / WebAssembly Swift SDK / Linux (nightly-6.3 Jammy)
Process completed with exit code 1.
|
|
Soundness / Documentation check
Process completed with exit code 1.
|
|
Release builds / Release builds / Linux (6.1)
Canceling since a higher priority waiting request for PR-refs/pull/453/merge-Release builds exists
|
|
Static Linux Swift SDK / Static SDK / Linux (latest-release Jammy)
Canceling since a higher priority waiting request for PR-refs/pull/453/merge-Static SDK exists
|
|
Release builds / Release builds / Windows (6.3)
Canceling since a higher priority waiting request for PR-refs/pull/453/merge-Release builds exists
|
|
Release builds / Release builds / Windows (6.3)
The operation was canceled.
|
|
Unit tests / Unit tests / Windows (nightly-main)
Canceling since a higher priority waiting request for PR-refs/pull/453/merge-Unit tests exists
|
|
Unit tests / Unit tests / Windows (nightly-main)
The operation was canceled.
|
|
Static Linux Swift SDK / Static SDK / Linux (main Jammy)
Canceling since a higher priority waiting request for PR-refs/pull/453/merge-Static SDK exists
|
|
Static Linux Swift SDK / Static SDK / Linux (main Jammy)
The operation was canceled.
|
|
Unit tests / Unit tests / Windows (6.2)
Canceling since a higher priority waiting request for PR-refs/pull/453/merge-Unit tests exists
|
|
Unit tests / Unit tests / Windows (6.2)
The operation was canceled.
|
|
Release builds / Release builds / Windows (6.2)
Canceling since a higher priority waiting request for PR-refs/pull/453/merge-Release builds exists
|
|
Release builds / Release builds / Windows (6.2)
The operation was canceled.
|
|
Unit tests / Unit tests / Windows (6.1)
Canceling since a higher priority waiting request for PR-refs/pull/453/merge-Unit tests exists
|
|
Unit tests / Unit tests / Windows (6.1)
The operation was canceled.
|
|
Unit tests / Unit tests / Windows (6.3)
Canceling since a higher priority waiting request for PR-refs/pull/453/merge-Unit tests exists
|
|
Unit tests / Unit tests / Windows (6.3)
The operation was canceled.
|
|
Release builds / Release builds / Windows (nightly-main)
Canceling since a higher priority waiting request for PR-refs/pull/453/merge-Release builds exists
|
|
Release builds / Release builds / Windows (nightly-main)
The operation was canceled.
|
|
Android Swift SDK / Android Swift SDK / Linux (main Jammy)
Canceling since a higher priority waiting request for PR-refs/pull/453/merge-Android Swift SDK exists
|
|
Android Swift SDK / Android Swift SDK / Linux (main Jammy)
The operation was canceled.
|
|
Release builds / Release builds / Windows (6.1)
Canceling since a higher priority waiting request for PR-refs/pull/453/merge-Release builds exists
|
|
Release builds / Release builds / Windows (6.1)
The operation was canceled.
|
|
Release builds / Release builds / Windows (nightly-next)
Canceling since a higher priority waiting request for PR-refs/pull/453/merge-Release builds exists
|
|
Release builds / Release builds / Windows (nightly-next)
The operation was canceled.
|
|
Unit tests / Unit tests / Windows (nightly-next)
Canceling since a higher priority waiting request for PR-refs/pull/453/merge-Unit tests exists
|
|
Unit tests / Unit tests / Windows (nightly-next)
The operation was canceled.
|
|
macOS benchmarks (NoTraits) / macOS (Xcode 26.1)
Process completed with exit code 1.
|
|
macOS benchmarks (NoTraits) / macOS (Xcode 16.4)
Process completed with exit code 1.
|
|
PR
Canceling since a higher priority waiting request for PR-refs/pull/453/merge-Unit tests exists
|
|
PR
Canceling since a higher priority waiting request for PR-refs/pull/453/merge-Release builds exists
|
|
PR
Canceling since a higher priority waiting request for PR-refs/pull/453/merge-Android Swift SDK exists
|
|
PR
Canceling since a higher priority waiting request for PR-refs/pull/453/merge-Static SDK exists
|
|
Soundness / Unacceptable language check
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/
|
|
Soundness / License headers check
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/
|
|
Soundness / YAML lint check
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/
|
|
Soundness / Broken symlinks check
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/
|
|
Soundness / Python lint check
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/
|
|
Soundness / Format check
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/
|
|
Soundness / Shell check
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/
|
|
Soundness / API breakage check
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/
|
|
Soundness / Documentation check
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/
|