Skip to content

feat: expose structured MCP command tools #2189

feat: expose structured MCP command tools

feat: expose structured MCP command tools #2189

Triggered via pull request May 27, 2026 19:55
Status Failure
Total duration 1m 46s
Artifacts

ci.yml

on: pull_request
iOS Runner Swift Compatibility
4s
iOS Runner Swift Compatibility
No test-only DI seams
4s
No test-only DI seams
Fallow Code Quality
17s
Fallow Code Quality
Unit Tests
50s
Unit Tests
Coverage
1m 42s
Coverage
Typecheck
25s
Typecheck
Android Helper Packages
41s
Android Helper Packages
Integration Tests
1m 1s
Integration Tests
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 6 warnings
Integration Tests
Process completed with exit code 1.
[provider-integration] test/integration/provider-scenarios/android-test-suite.test.ts > Provider-backed integration Android Maestro replay uses fresh selector snapshots and content-lane swipes: src/daemon-error.ts#L5
Error: test does not support this file type: /var/folders/8j/sfr9qqcj73j4p6nhwcfpr0th0000gn/T/agent-device-provider-scenario-android-deploy-IUs5Y5/suite-maestro/maestro-flow.yaml ❯ throwDaemonError src/daemon-error.ts:5:9 ❯ execute src/client.ts:65:7 ❯ executeCommand src/client.ts:81:13 ❯ Object.test src/client.ts:286:32 ❯ test/integration/provider-scenarios/android-test-suite.test.ts:105:21 ❯ withProviderScenarioResource test/integration/provider-scenarios/harness.ts:85:12 ❯ test/integration/provider-scenarios/android-test-suite.test.ts:74:3 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { code: 'INVALID_ARGS', details: { hint: 'Check command arguments and run --help for usage examples.', diagnosticId: 'mpohiinc-102fa013', logPath: '/Users/runner/.agent-device/logs/default/2026-05-27/2026-05-27T19-56-14-185Z-mpohiinc-102fa013.ndjson' } }
Coverage
Process completed with exit code 1.
[provider-integration] test/integration/provider-scenarios/android-test-suite.test.ts > Provider-backed integration Android Maestro replay uses fresh selector snapshots and content-lane swipes: src/daemon-error.ts#L5
Error: test does not support this file type: /var/folders/8j/sfr9qqcj73j4p6nhwcfpr0th0000gn/T/agent-device-provider-scenario-android-deploy-s7ThmK/suite-maestro/maestro-flow.yaml ❯ throwDaemonError src/daemon-error.ts:5:9 ❯ execute src/client.ts:65:7 ❯ executeCommand src/client.ts:81:13 ❯ Object.test src/client.ts:286:32 ❯ test/integration/provider-scenarios/android-test-suite.test.ts:105:21 ❯ withProviderScenarioResource test/integration/provider-scenarios/harness.ts:85:12 ❯ test/integration/provider-scenarios/android-test-suite.test.ts:74:3 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { code: 'INVALID_ARGS', details: { hint: 'Check command arguments and run --help for usage examples.', diagnosticId: 'mpohi3b6-1d3e4f62', logPath: '/Users/runner/.agent-device/logs/default/2026-05-27/2026-05-27T19-55-54-307Z-mpohi3b6-1d3e4f62.ndjson' } }
Fallow Code Quality
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/
Typecheck
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/
Android Helper Packages
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/
Unit Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/
Integration Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/
Coverage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/