Skip to content

fix: drop use_fuzzy_matching from tap_on MCP schema #2379

fix: drop use_fuzzy_matching from tap_on MCP schema

fix: drop use_fuzzy_matching from tap_on MCP schema #2379

Triggered via pull request April 15, 2026 20:48
Status Success
Total duration 31m 47s
Artifacts 6

test-e2e.yaml

on: pull_request
Matrix: build
Test on Web
2m 26s
Test on Web
Test on Android
22m 8s
Test on Android
Test on iOS
11m 48s
Test on iOS
Test on iOS (XCTest Runner only)
0s
Test on iOS (XCTest Runner only)
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
Build on Java 17
No files were found with the provided path: build/Products. No artifacts will be uploaded.
Build on Java 17: maestro-ios-xctest-runner/maestro-driver-iosUITests/Routes/XCTest/AXClientSwizzler.swift#L34
use '#selector' instead of explicitly constructing a 'Selector'
Build on Java 17: maestro-ios-xctest-runner/maestro-driver-iosUITests/Routes/XCTest/AXClientSwizzler.swift#L21
use '#selector' instead of explicitly constructing a 'Selector'
Build on Java 17: maestro-ios-xctest-runner/maestro-driver-iosUITests/Routes/XCTest/AXClientSwizzler.swift#L34
use '#selector' instead of explicitly constructing a 'Selector'
Build on Java 17: maestro-ios-xctest-runner/maestro-driver-iosUITests/Routes/XCTest/AXClientSwizzler.swift#L21
use '#selector' instead of explicitly constructing a 'Selector'
Build on Java 17: maestro-ios-xctest-runner/maestro-driver-iosUITests/Routes/XCTest/AXClientSwizzler.swift#L34
use '#selector' instead of explicitly constructing a 'Selector'
Build on Java 17: maestro-ios-xctest-runner/maestro-driver-iosUITests/Routes/XCTest/AXClientSwizzler.swift#L21
use '#selector' instead of explicitly constructing a 'Selector'
Build on Java 17: maestro-ios-xctest-runner/maestro-driver-iosUITests/Routes/XCTest/AXClientSwizzler.swift#L34
use '#selector' instead of explicitly constructing a 'Selector'
Build on Java 17: maestro-ios-xctest-runner/maestro-driver-iosUITests/Routes/XCTest/AXClientSwizzler.swift#L21
use '#selector' instead of explicitly constructing a 'Selector'
Test on Android
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 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/

Artifacts

Produced during runtime
Name Size Digest
maestro-cli-jdk17-run_id24477598176 Expired
203 MB
sha256:e79e3a9c7365f5673891617601adf143fc48e38af5dbe78825aa3517a82e16ea
maestro-root-dir-android Expired
853 KB
sha256:08c9d8fcbf8a77140b2dfc46395525799dbe81b99135c31480c9cf48af1d662e
maestro-root-dir-ios Expired
200 KB
sha256:0d6f1799371bccbca43ca97774e557ad0bf0fd69ae90751e9485cbe0320a849f
maestro-root-dir-web Expired
201 KB
sha256:a7f7132c317e36982253ca2ddef1356aadfb019db4645c3a541b2db3c949c27f
maestro-screenrecord-ios.mp4 Expired
17.4 MB
sha256:c273b0cb6f783ee859c0e0c55872cb2f2fa1ecf600247778c45269869eb2d093
xctest_runner_logs Expired
22.6 KB
sha256:359d2cc511d85edf5a843d23738c3f4b451b578998b01feaaf972fc543d04c6e