Skip to content

feat: use Selenium's Bridge.add_command for custom command registrati… #477

feat: use Selenium's Bridge.add_command for custom command registrati…

feat: use Selenium's Bridge.add_command for custom command registrati… #477

Triggered via push March 22, 2026 05:33
Status Failure
Total duration 27m 6s
Artifacts 20
ios_test_with_other_deps
11m 17s
ios_test_with_other_deps
Matrix: android_test
Matrix: ios_test
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 8 warnings
android_test (test/functional/android/android/mjpeg_server_test.rb,test/functional/android/androi...
The process '/usr/bin/sh' failed with exit code 1
ios_test_with_other_deps
Process completed with exit code 1.
ios_test (test/functional/ios/ios/device_wda_attachment_test.rb,test/functional/ios/ios/search_co...
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 2nd, 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/
ios_test (test/functional/ios/ios/image_comparison_test.rb, test6, ios, WebDriverAgentRunner-Runn...
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 2nd, 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/
ios_test (test/functional/ios/webdriver/device_test.rb, test3, ios, WebDriverAgentRunner-Runner.app)
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 2nd, 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/
ios_test_with_other_deps
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 2nd, 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/
ios_test (test/functional/ios/tv_driver_test.rb, test7, tvOS, WebDriverAgentRunner_tvOS-Runner.app)
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 2nd, 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/
ios_test (test/functional/ios/ios/device_test.rb, test4, ios, WebDriverAgentRunner-Runner.app)
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 2nd, 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/
ios_test (test/functional/ios/webdriver/create_session_test.rb,test/functional/ios/webdriver/w3c_...
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 2nd, 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/
ios_test (test/functional/ios/driver_test.rb,test/functional/ios/patch_test.rb, test1, ios, WebDr...
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 2nd, 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
appium-android-espresso-test10.log
206 KB
sha256:16fedf7491514ae90587be07ad818553817bf526abcc88e079c51c5dbfbb6a23
appium-android-espresso-test12.log
822 Bytes
sha256:7a936e558afbeb4177f3d753060a8f8419fbd7d86a332d5ac526e73fef6688ce
appium-android-espresso-test2.log
427 KB
sha256:4ed94dd1a4632997b9624179f81221761c80d0fd71984e7ab2e65ed660104f1a
appium-android-espresso-test4.log
77.8 KB
sha256:c361b637e963714295d60cd5896cf1c828b3c0a4e7b31c7e3a8faad5f454d9e4
appium-android-espresso-test6.log
61 KB
sha256:faf3c30d2ed308891d15df4118621350ac2a289275d8bb2b2f1a555f855fc5ac
appium-android-espresso-test8.log
259 KB
sha256:a6ac1d1ae3a52f3588bd894d74ddd48ffbe451bc5547b424a07323585beaea6a
appium-android-uiautomator2-test1.log
429 KB
sha256:68687fe37ff8f86e186e7d830010e560660ae0e59afa798d49c7696d219ea71d
appium-android-uiautomator2-test11.log
840 Bytes
sha256:1c9b9da05a29e71da759272d25c5e7739b04d2617cf6205627d7d9e2246104dd
appium-android-uiautomator2-test3.log
92.6 KB
sha256:7604a9396f7250966780bf003eaa5d317e4ef4000440161f5b55be1099b60145
appium-android-uiautomator2-test5.log
13.1 KB
sha256:ff61833069576d0ca159712f9428fea580ca945a6b138700a5d5193c7b61d577
appium-android-uiautomator2-test7.log
112 KB
sha256:41dd9985a576bd08a9f959e538950b5fd88b198aab370ece4e9db12bbd977eb4
appium-android-uiautomator2-test9.log
151 KB
sha256:d19d40599ecb9ec60c164ab446c3f12384858b5cff734c3c9b80c17767b37325
appium-ios-test1.log
567 KB
sha256:8c58d92f2eb82e33a0fc491d1c11874a5bc0610e39ffa233a1d7f49cbde2a5a1
appium-ios-test2.log
29.2 KB
sha256:4ad2525522c9f152601c6741e7574260074f4aac45b8282dd6e0e07bdd333f53
appium-ios-test3.log
547 KB
sha256:40e975a8607e52393cd05a8b02b933a97af31de1b580495cc481570ffbe6e99a
appium-ios-test4.log
598 KB
sha256:949f5c4a108097f26ecf2e5b586918641b8595b0eb29770d8402ff25264208df
appium-ios-test5.log
15.9 KB
sha256:c6fc3c4cea9f3395b8bf92703c7c1e79a110167866a7d6bf53d8c97b9374c0fa
appium-ios-test6.log
40.6 KB
sha256:3d0b3193f6ff48d5770c5d8c05767461db3b04a1030cd64046f14b58a5f56778
appium-ios-test7.log
8.42 KB
sha256:30585386676a4c8460fe91bfd48c97518bb6cae65db1757d2bc84b4267b604cd
appium-ios_test_with_other_deps.log
561 KB
sha256:cb153f234fa1ba3e84b02b47e6bf71897b1d194f86f98427edf2b4e3a796b9c7