cache downloads in ~/.flet/cache (FLET_CACHE_DIR) across all plugins #233

Triggered via push June 11, 2026 15:04

FeodorFitsner

pushed 6a87c5e

dart-bridge

Status Cancelled

Total duration 1h 45m 57s

Artifacts –

ci.yml

on: push

Matrix: android

Matrix: bridge_example_android

Matrix: bridge_example_ios

Matrix: bridge_example_linux

Matrix: bridge_example_macos

Matrix: bridge_example_windows

Matrix: ios

Matrix: linux

Matrix: macos

Matrix: windows

Matrix: flet_ffi_android

Matrix: flet_ffi_ios

Matrix: flet_ffi_linux

Matrix: flet_ffi_macos

Matrix: flet_ffi_windows

Publish to pub.dev

Annotations

9 errors, 21 warnings, and 6 notices

Test Flet FFI example on Windows (Python 3.14)

Process completed with exit code 1.

Test Flet FFI example on Windows (Python 3.14)

0 tests passed, 1 failed.

Test Flet FFI example on Windows (Python 3.13)

Process completed with exit code 1.

Test Flet FFI example on Windows (Python 3.13)

0 tests passed, 1 failed.

Test Flet FFI example on Windows (Python 3.12)

Process completed with exit code 1.

Test Flet FFI example on Windows (Python 3.12)

0 tests passed, 1 failed.

Test Flet FFI example on iOS (Python 3.14)

The run was canceled by @FeodorFitsner.

Test Flet FFI example on iOS (Python 3.14)

The operation was canceled.

The run was canceled by @FeodorFitsner.

Test Flet FFI example on Linux AMD64 (Python 3.13)

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, astral-sh/setup-uv@v6. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/

Test Flet FFI example on Linux AMD64 (Python 3.12)

Test Flet FFI example on Linux ARM64 (Python 3.14)

Test Flet FFI example on Linux ARM64 (Python 3.13)

Test Flet FFI example on Linux ARM64 (Python 3.12)

Test Flet FFI example on Linux AMD64 (Python 3.14)

Test Flet FFI example on Windows (Python 3.14)

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 16th, 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/

Test Flet FFI example on macOS (Python 3.12)

Test Flet FFI example on macOS (Python 3.13)

Test Flet FFI example on macOS (Python 3.14)

Test Flet FFI example on Windows (Python 3.13)

Test Flet FFI example on Windows (Python 3.12)

Test Flet FFI example on Android (Python 3.12)

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, gradle/actions/setup-gradle@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/

Test Flet FFI example on Android (Python 3.12)

Failed to restore gradle-home-v1|Linux|flet_ffi_android[c40587f601dfb73f9636ff3c5df6641a]-6a87c5e091f7d108aab98143a0aef9003c485a35: Error: Cache service responded with 400

Test Flet FFI example on Android (Python 3.14)

Failed to restore gradle-home-v1|Linux|flet_ffi_android[c8b79c1b6fa9dceecd109ea883d68974]-6a87c5e091f7d108aab98143a0aef9003c485a35: Error: Cache service responded with 400

Test Flet FFI example on Android (Python 3.13)

Failed to restore gradle-home-v1|Linux|flet_ffi_android[1eaa53f85d1829ea3efb6e27faaadd67]-6a87c5e091f7d108aab98143a0aef9003c485a35: Error: Cache service responded with 400

Test Flet FFI example on iOS (Python 3.12)

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, futureware-tech/simulator-action@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/

Test Flet FFI example on iOS (Python 3.13)

Test Flet FFI example on iOS (Python 3.14)

Test Flet FFI example on Windows (Python 3.14)