Skip to content

fix: throw correct test error in case of invalid timeout #2377

fix: throw correct test error in case of invalid timeout

fix: throw correct test error in case of invalid timeout #2377

Triggered via pull request April 15, 2026 18:56
Status Success
Total duration 21m 18s
Artifacts 6

test-e2e.yaml

on: pull_request
Matrix: build
Test on Web
2m 33s
Test on Web
Test on Android
16m 49s
Test on Android
Test on iOS
11m 43s
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_id24472532999 Expired
203 MB
sha256:0af6a42168b1db6d797e86802ac6583b371b7b71f542760ee5b2d368ee065a8a
maestro-root-dir-android Expired
816 KB
sha256:12bc59e2b23d094fcc3d5e65dda9152101ae783fc343b5ee3cdcb0de5db884b1
maestro-root-dir-ios Expired
200 KB
sha256:78399abb00cc103f5c1eda129e1dd4311f2b0a1dde4450dcd6928b615b5da98b
maestro-root-dir-web Expired
201 KB
sha256:4246b618dc59fd0d967ac4b46314f22bb03f783a21b8e784ff1796d6eed0f979
maestro-screenrecord-ios.mp4 Expired
20.9 MB
sha256:1050fb6eba845acf5b056c465d02f740428bd4dc7ab851ba3ace12c17e489eb6
xctest_runner_logs Expired
23.7 KB
sha256:d130569f3b8ff167b3c712c88b8c4004513efcf167ae8c63dc63bc5f1a470647