Skip to content

feat: use Selenium's Bridge.add_command for custom command registration #476

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

feat: use Selenium's Bridge.add_command for custom command registration #476

Triggered via pull request March 22, 2026 02:06
Status Failure
Total duration 25m 9s
Artifacts 20

functional-test.yml

on: pull_request
ios_test_with_other_deps
16m 1s
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/webdriver/create_session_test.rb,test/functional/android/we...
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/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/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/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/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/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/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/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
201 KB
sha256:bb842dba7350c37a5e4edfdfcb16ca13fdab0026381b5182242cb9e3ba0e8988
appium-android-espresso-test12.log
826 Bytes
sha256:d35cf0c64193c46f5220f92cc884085d38dac514aae711aac48398223b653639
appium-android-espresso-test2.log
436 KB
sha256:e35f6778df6742d62a67eb5e45e32b22fc8fe62c11f1cc8901363d8e75fc0fa6
appium-android-espresso-test4.log
164 KB
sha256:c3de1afd4b4385590ee5918a314e3832f39e34d315535ef1cca8f840856f0657
appium-android-espresso-test6.log
61.4 KB
sha256:4fb929944814c041e567a949d13d32bd17d2eb6bb351a0a5dc5b95b8842f3c7b
appium-android-espresso-test8.log
258 KB
sha256:337a4f59ccf80932cab47dae2015531625901c64511dc0137ee3079814fd12a9
appium-android-uiautomator2-test1.log
446 KB
sha256:f97debe88ba65640eedfe87fd53acee48c18f15e505929ae1479f63057c2d664
appium-android-uiautomator2-test11.log
828 Bytes
sha256:4ff5e4357fcf25a4e90ebde8e26beb549c739b4432a4cf2f1cf75e0c7da7a476
appium-android-uiautomator2-test3.log
92.3 KB
sha256:94cc52204c51529dec42e5507d888707e2e7f056ac9703deb2de1b7c0b78b5db
appium-android-uiautomator2-test5.log
13.1 KB
sha256:3f8e1cdeb78f31cf7c750086d592e565ea438f87b14b44d772e871c871ac161b
appium-android-uiautomator2-test7.log
111 KB
sha256:8eb6c010a048fe665476cef4ab42d9d6c470196d15ced96dce820ddfac0078e9
appium-android-uiautomator2-test9.log
109 KB
sha256:f901b025f29642dabf771042f7d2c011182b74c8ab4c27df1d618ff9d49836dc
appium-ios-test1.log
59 KB
sha256:e637f31aa6f85268cc70c1f9a3b946792997e69856f279cb576d5ef8eaab0f87
appium-ios-test2.log
25.9 KB
sha256:9a75359958f7ccca83920ad2483fb3393cc3dc73f29724aaec4f0f652e9a9a7a
appium-ios-test3.log
555 KB
sha256:04219aa4ecb7cee12b757b0715519de18c001567aaf7e3b775bef703fb213948
appium-ios-test4.log
587 KB
sha256:b911787876fb86141da9d8e21404921b5c0d8b25f6d55eb4483340b5876b0b08
appium-ios-test5.log
15.2 KB
sha256:a2f2070919f4b32f9604e42b581fd324111124ec58335cd451156f3e34f4ffc4
appium-ios-test6.log
32.9 KB
sha256:5862ce6b62cd3014610da09202fd2ab0b250f8e1d0398ae13772b83dbfdb9801
appium-ios-test7.log
8.35 KB
sha256:fa579004c2117ac00895d808ddbab1e6934c09cc4c6267ab96f558a24e889d96
appium-ios_test_with_other_deps.log
558 KB
sha256:51b7d7d4736b0d595095c45bb9791724d314b68a13e43a8a2c435450e9580f44