Skip to content

converted obamenu from python 2 to 3 using 2to3 tool to fix Invalid output from pipe-menu "obamenu" #280

converted obamenu from python 2 to 3 using 2to3 tool to fix Invalid output from pipe-menu "obamenu"

converted obamenu from python 2 to 3 using 2to3 tool to fix Invalid output from pipe-menu "obamenu" #280

Triggered via pull request March 24, 2026 08:16
Status Cancelled
Total duration 2m 13s
Artifacts 2

main.yml

on: pull_request
nightly-link
3s
nightly-link
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

12 errors, 7 warnings, and 1 notice
build (macos-13, none)
The configuration 'macos-13-us-default' is not supported
build (macos-14, none)
Failed to get ID token: Error message: Unable to get ACTIONS_ID_TOKEN_REQUEST_URL env variable
build (ubuntu-24.04, 3.1)
The strategy configuration was canceled because "build.macos-14_none" failed
build (ubuntu-24.04, 3.1)
The operation was canceled.
build (windows-2022, 3.1)
The strategy configuration was canceled because "build.macos-14_none" failed
build (windows-2022, 3.1)
The operation was canceled.
build (ubuntu-22.04, 3.1)
The strategy configuration was canceled because "build.macos-14_none" failed
build (ubuntu-22.04, 3.1)
The operation was canceled.
build (windows-2025, 3.1)
The strategy configuration was canceled because "build.macos-14_none" failed
build (windows-2025, 3.1)
The operation was canceled.
build (macos-15, none)
The strategy configuration was canceled because "build.macos-14_none" failed
build (macos-15, none)
The operation was canceled.
Workflow syntax warning: .github/workflows/main.yml#L298
.github/workflows/main.yml (Line: 298, Col: 9): Conditional expression contains literal text outside replacement tokens. This will cause the expression to always evaluate to truthy. Did you mean to put the entire expression inside ${{ }}?
build (macos-14, none)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/attest-build-provenance/predicate@1176ef556905f349f669722abf30bce1a6e16e01, actions/cache@v4.2.3, actions/checkout@v4.2.2, actions/upload-artifact@v4.6.2, carlkidcrypto/os-specific-runner@v2.1.2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
build (ubuntu-24.04, 3.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/cache@v4.2.3, actions/checkout@v4.2.2, carlkidcrypto/os-specific-runner@v2.1.2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
build (windows-2022, 3.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4.2.3, actions/checkout@v4.2.2, carlkidcrypto/os-specific-runner@v2.1.2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
build (ubuntu-22.04, 3.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/cache@v4.2.3, actions/checkout@v4.2.2, carlkidcrypto/os-specific-runner@v2.1.2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
build (windows-2025, 3.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4.2.3, actions/checkout@v4.2.2, carlkidcrypto/os-specific-runner@v2.1.2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
build (macos-15, none)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4.2.3, actions/checkout@v4.2.2, carlkidcrypto/os-specific-runner@v2.1.2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Download the artificats from nightly.link (without logging in) by visiting the URL below
https://nightly.link/RemoteConnectionManager/RCM/actions/runs/23479646939

Artifacts

Produced during runtime
Name Size Digest
RCM-client--macos-14_arm64--4746d453ffcc10d506f54c208b77aa80ac905353
29.5 MB
sha256:ec893b109b8f5b6ea400a14cb5252067085b35384f637f327f5c0462fbf9a347
RCM-client--macos-14_arm64--4746d453ffcc10d506f54c208b77aa80ac905353-dir
50.6 MB
sha256:fa3f66120602a0448808f62c6f6bc337c354e4bd6185dbd70ed927533d855b2b