Skip to content

CirrusCI: Fix ranlib confusion between xcode and AndroidNDK #6750

CirrusCI: Fix ranlib confusion between xcode and AndroidNDK

CirrusCI: Fix ranlib confusion between xcode and AndroidNDK #6750

Triggered via pull request April 7, 2026 18:06
Status Cancelled
Total duration 36m 0s
Artifacts

dynamic_arch.yml

on: pull_request
Matrix: build
Matrix: cross_build
Matrix: msys2
Fit to window
Zoom out
Zoom in

Annotations

32 errors and 10 warnings
cross_build (mipsel, mipsel-linux-gnu, TARGET=MIPS1004K)
Canceling since a higher priority waiting request for continuous build-m1xbuild_tahoe exists
build (ubuntu-latest, gcc, flang, cmake)
Canceling since a higher priority waiting request for continuous build-m1xbuild_tahoe exists
build (ubuntu-latest, gcc, gfortran, cmake)
Canceling since a higher priority waiting request for continuous build-m1xbuild_tahoe exists
build (ubuntu-latest, gcc, flang, make)
Canceling since a higher priority waiting request for continuous build-m1xbuild_tahoe exists
build (ubuntu-latest, gcc, gfortran, make)
Canceling since a higher priority waiting request for continuous build-m1xbuild_tahoe exists
msys2 (CLANG64, int64, Release)
Canceling since a higher priority waiting request for continuous build-m1xbuild_tahoe exists
build (ubuntu-latest, clang, gfortran, make)
Canceling since a higher priority waiting request for continuous build-m1xbuild_tahoe exists
build (ubuntu-latest, clang, flang, make)
Canceling since a higher priority waiting request for continuous build-m1xbuild_tahoe exists
cross_build (alpha, alpha-linux-gnu, TARGET=EV4)
Canceling since a higher priority waiting request for continuous build-m1xbuild_tahoe exists
build (ubuntu-latest, clang, flang, cmake)
Canceling since a higher priority waiting request for continuous build-m1xbuild_tahoe exists
build (ubuntu-latest, clang, gfortran, cmake)
Canceling since a higher priority waiting request for continuous build-m1xbuild_tahoe exists
msys2 (UCRT64, int32, None, mingw-w64-ucrt-x86_64, fc)
Canceling since a higher priority waiting request for continuous build-m1xbuild_tahoe exists
build (ubuntu-latest, clang-21, gfortran, make)
Canceling since a higher priority waiting request for continuous build-m1xbuild_tahoe exists
build (ubuntu-latest, clang-21, flang, cmake)
Canceling since a higher priority waiting request for continuous build-m1xbuild_tahoe exists
build (ubuntu-latest, clang-21, flang, make)
Canceling since a higher priority waiting request for continuous build-m1xbuild_tahoe exists
build (ubuntu-latest, clang-21, gfortran, cmake)
Canceling since a higher priority waiting request for continuous build-m1xbuild_tahoe exists
build (ubuntu-24.04-arm, clang-21, gfortran, cmake)
Canceling since a higher priority waiting request for continuous build-m1xbuild_tahoe exists
build (macos-latest, clang, gfortran, make)
Canceling since a higher priority waiting request for continuous build-m1xbuild_tahoe exists
build (ubuntu-24.04-arm, clang, gfortran, cmake)
Canceling since a higher priority waiting request for continuous build-m1xbuild_tahoe exists
build (ubuntu-24.04-arm, clang-21, gfortran, make)
Canceling since a higher priority waiting request for continuous build-m1xbuild_tahoe exists
msys2 (UCRT64, int64, Release)
Canceling since a higher priority waiting request for continuous build-m1xbuild_tahoe exists
msys2 (UCRT64, int64, Release)
The operation was canceled.
msys2 (MINGW32, int32, Release)
Canceling since a higher priority waiting request for continuous build-m1xbuild_tahoe exists
msys2 (MINGW32, int32, Release)
The operation was canceled.
msys2 (UCRT64, int32, Release)
Canceling since a higher priority waiting request for continuous build-m1xbuild_tahoe exists
msys2 (UCRT64, int32, Release)
The operation was canceled.
msys2 (CLANG64, int32, Release)
Canceling since a higher priority waiting request for continuous build-m1xbuild_tahoe exists
msys2 (CLANG64, int32, Release)
The operation was canceled.
build (macos-latest, clang, gfortran, cmake)
Canceling since a higher priority waiting request for continuous build-m1xbuild_tahoe exists
build (macos-latest, clang, gfortran, cmake)
The operation was canceled.
build (ubuntu-24.04-arm, gcc, gfortran, cmake)
Canceling since a higher priority waiting request for continuous build-m1xbuild_tahoe exists
continuous build
Canceling since a higher priority waiting request for continuous build-m1xbuild_tahoe exists
neoverse_build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. 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/
build (ubuntu-24.04-arm, gcc, gfortran, make)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3. 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/
cross_build (riscv64, riscv64-linux-gnu, TARGET=RISCV64_GENERIC)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3. 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/
build (ubuntu-24.04-arm, clang, gfortran, make)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3. 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/
cross_build (mips64el, mips64el-linux-gnuabi64, DYNAMIC_ARCH=1 TARGET=GENERIC)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3. 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/
msys2 (UCRT64, int64, Release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/checkout@v3. 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/
msys2 (MINGW32, int32, Release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/checkout@v3. 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/
msys2 (UCRT64, int32, Release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/checkout@v3. 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/
msys2 (CLANG64, int32, Release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/checkout@v3. 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/
build (macos-latest, clang, gfortran, cmake)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3. 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/