ci(bridge_example): invoke each integration test file separately #245
FeodorFitsnerci.yml
on: push
Matrix: bridge_example_android
Matrix: bridge_example_ios
Matrix: bridge_example_linux
Matrix: bridge_example_macos
Matrix: bridge_example_windows
Publish to pub.dev
Annotations
6 errors, 9 warnings, and 6 notices
|
Test Bridge example on Linux AMD64 (Python 3.14)
Process completed with exit code 1.
|
|
Test Bridge example on Linux AMD64 (Python 3.12)
Process completed with exit code 1.
|
|
Test Bridge example on Linux ARM64 (Python 3.13)
Process completed with exit code 1.
|
|
Test Bridge example on iOS (Python 3.13)
Canceling since a higher priority waiting request for CI-refs/heads/dart-bridge exists
|
|
Test Bridge example on iOS (Python 3.13)
The operation was canceled.
|
|
CI
Canceling since a higher priority waiting request for CI-refs/heads/dart-bridge exists
|
|
Test Bridge example on Android (Python 3.14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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 Bridge example on Android (Python 3.14)
Failed to restore gradle-home-v1|Linux|bridge_example_android[c8b79c1b6fa9dceecd109ea883d68974]-5c7c940e5ae20c3c414ed19e4b00f25beee9c40f: Error: Cache service responded with 400
|
|
Test Bridge 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: 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 Bridge example on Android (Python 3.12)
Failed to restore gradle-home-v1|Linux|bridge_example_android[c40587f601dfb73f9636ff3c5df6641a]-5c7c940e5ae20c3c414ed19e4b00f25beee9c40f: Error: Cache service responded with 400
|
|
Test Bridge example on Android (Python 3.13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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 Bridge example on Android (Python 3.13)
Failed to restore gradle-home-v1|Linux|bridge_example_android[1eaa53f85d1829ea3efb6e27faaadd67]-5c7c940e5ae20c3c414ed19e4b00f25beee9c40f: Error: Cache service responded with 400
|
|
Test Bridge example on iOS (Python 3.14)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: futureware-tech/simulator-action@v5. 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 Bridge 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: futureware-tech/simulator-action@v5. 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 Bridge example on iOS (Python 3.13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: futureware-tech/simulator-action@v5. 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 Bridge example on Windows (Python 3.13)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Test Bridge example on Windows (Python 3.13)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Test Bridge example on Windows (Python 3.12)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Test Bridge example on Windows (Python 3.12)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Test Bridge example on Windows (Python 3.14)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Test Bridge example on Windows (Python 3.14)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|