search

zebrunner / appium

Enhanced Appium for Elastic Selenium Grid/MCloud services
8 stars 3 forks source link

500 error: unable to run Web-Demo-Test on mobile devices with browserName=chrome #375

Closed dhreben closed 4 months ago

dhreben commented 5 months ago

Steps:

  1. Open Jenkins
  2. Run Web-Demo-Test with browserName=chrome

Actual result: unknown error: Failed to run adb command with networking error: net::ERR_ADDRESS_INVALID. Is the adb server running?

Appium log:

2024-04-23 13:14:24:916 - [HTTP] 
2024-04-23 13:14:27:536 - [HTTP] --> GET /wd/hub/status-adb
2024-04-23 13:14:27:536 - [HTTP] {"exitCode":101}
2024-04-23 13:14:27:551 - [HTTP] <-- GET /wd/hub/status-adb 200 15 ms - 105
2024-04-23 13:14:27:551 - [HTTP] 
2024-04-23 13:14:27:608 - [HTTP] --> POST /wd/hub/session
2024-04-23 13:14:27:608 - [HTTP] {"desiredCapabilities":{"server:CONFIG_UUID":"775622f0-214a-4aba-b0ac-e79b422d4c04","appium:locale":"US","browserName":"chrome","zebrunner:slotCapabilities":{"deviceType":"TV","proxy_port":7443,"server:CONFIG_UUID":"775622f0-214a-4aba-b0ac-e79b422d4c04","seleniumProtocol":"WebDriver","server_proxy_port":7444,"adb_port":7442,"deviceName":"HTC_U_Ultra","platform":"ANDROID","platformVersion":"7.0","automationName":"uiautomator2","remoteURL":null,"maxInstances":1,"platformName":"android","udid":"FA7371702902"},"appium:language":"en","appium:remoteAppsCacheLimit":0,"appium:deviceName":"HTC_U_Ultra","platformName":"android","appium:automationName":"UIAutomator2","appium:app":"https://qaprosoft.s3-us-west-2.amazonaws.com/carinademoexample.apk"},"capabilities":{"firstMatch":[{"appium:app":"https://qaprosoft.s3-us-west-2.amazonaws.com/carinademoexample.apk","appium:automationName":"UIAutomator2","appium:deviceName":"HTC_U_Ultra","appium:language":"en","appium:locale":"US","appium:remoteAppsCacheLimit":0,"browserNam...
2024-04-23 13:14:27:610 - [Appium] Attempting to find matching driver for automationName 'UIAutomator2' and platformName 'android'
2024-04-23 13:14:27:610 - [Appium] The 'uiautomator2' driver was installed and matched caps.
2024-04-23 13:14:27:610 - [Appium] Will require it at /usr/lib/node_modules/appium/node_modules/appium-uiautomator2-driver
2024-04-23 13:14:27:610 - [AppiumDriver@7108] Appium v2.2.2 creating new AndroidUiautomator2Driver (v3.1.0) session
2024-04-23 13:14:27:610 - [AppiumDriver@7108] Checking BaseDriver versions for Appium and AndroidUiautomator2Driver
2024-04-23 13:14:27:610 - [AppiumDriver@7108] Appium's BaseDriver version is 9.4.3
2024-04-23 13:14:27:610 - [AppiumDriver@7108] AndroidUiautomator2Driver's BaseDriver version is 9.4.3
2024-04-23 13:14:27:614 - [AppiumDriver@7108] Applying relaxed security to 'AndroidUiautomator2Driver' as per server command line argument. All insecure features will be enabled unless explicitly disabled by --deny-insecure
2024-04-23 13:14:27:614 - [AppiumDriver@7108] Explicitly enabling use of insecure features:
2024-04-23 13:14:27:614 - [AppiumDriver@7108]     chromedriver_autodownload
2024-04-23 13:14:27:621 - [AndroidUiautomator2Driver@ba52] The following provided capabilities were not recognized by this driver:
2024-04-23 13:14:27:621 - [AndroidUiautomator2Driver@ba52]   server:CONFIG_UUID
2024-04-23 13:14:27:621 - [AndroidUiautomator2Driver@ba52]   zebrunner:slotCapabilities
2024-04-23 13:14:27:621 - [AndroidUiautomator2Driver@ba52] The desired capabilities should generally not include both an 'app' and a 'browserName'
2024-04-23 13:14:27:621 - [AndroidUiautomator2Driver@ba52 (b42df425)] Session created with session id: b42df425-c11e-436a-a22a-fc2b60ce8bff
2024-04-23 13:14:27:622 - [ADB] Using 'adb' from '/opt/android/platform-tools/adb'
2024-04-23 13:14:27:633 - [AndroidUiautomator2Driver@ba52 (b42df425)] Retrieving device list
2024-04-23 13:14:27:643 - [AndroidUiautomator2Driver@ba52 (b42df425)] Using device: FA7371702902
2024-04-23 13:14:27:644 - [ADB] Using 'adb' from '/opt/android/platform-tools/adb'
2024-04-23 13:14:27:656 - [AndroidUiautomator2Driver@ba52 (b42df425)] We're going to run a Chrome-based session
2024-04-23 13:14:27:871 - [AndroidUiautomator2Driver@ba52 (b42df425)] Chrome-type package and activity are com.android.chrome and com.android.chrome/com.google.android.apps.chrome.Main
2024-04-23 13:14:27:871 - [BaseDriver] Using downloadable app 'https://qaprosoft.s3-us-west-2.amazonaws.com/carinademoexample.apk'
2024-04-23 13:14:28:463 - [BaseDriver] [MCLOUD] Target path [getLocalFileForAppUrl]: /opt/appium-storage/carinademoexample.apk
2024-04-23 13:14:28:464 - [BaseDriver] [MCLOUD] Local version of app was found. Will check actuality of the file
2024-04-23 13:14:29:159 - [BaseDriver] [MCLOUD] Remote file size is 9328742 and local file size is 9328742
2024-04-23 13:14:29:160 - [BaseDriver] [MCLOUD] Sizes are the same. Hence will use already stored application for the session
2024-04-23 13:14:29:217 - [AndroidUiautomator2Driver@ba52 (b42df425)] Capability 'appActivity' is expected to only include latin letters, digits, underscore, dot, comma and asterisk characters.
2024-04-23 13:14:29:217 - [AndroidUiautomator2Driver@ba52 (b42df425)] Current value 'com.android.chrome/com.google.android.apps.chrome.Main' has non-matching character at index 18: 'com.android.chrome/'
2024-04-23 13:14:29:917 - [HTTP] --> GET /wd/hub/status
2024-04-23 13:14:29:917 - [HTTP] {}
2024-04-23 13:14:29:918 - [HTTP] <-- GET /wd/hub/status 200 0 ms - 110
2024-04-23 13:14:29:918 - [HTTP] 
2024-04-23 13:14:29:938 - [AndroidUiautomator2Driver@ba52 (b42df425)] Performing fast reset on 'com.android.chrome'
2024-04-23 13:14:30:683 - [AndroidUiautomator2Driver@ba52 (b42df425)] Server packages are not going to be (re)installed
2024-04-23 13:14:31:290 - [ADB] Adding packages ["io.appium.settings","io.appium.uiautomator2.server","io.appium.uiautomator2.server.test"] to Doze whitelist
2024-04-23 13:14:32:963 - [AndroidUiautomator2Driver@ba52 (b42df425)] Starting UIAutomator2 server 7.0.5
2024-04-23 13:14:32:964 - [AndroidUiautomator2Driver@ba52 (b42df425)] Using UIAutomator2 server from '/usr/lib/node_modules/appium/node_modules/appium-uiautomator2-driver/node_modules/appium-uiautomator2-server/apks/appium-uiautomator2-server-v7.0.5.apk' and test from '/usr/lib/node_modules/appium/node_modules/appium-uiautomator2-driver/node_modules/appium-uiautomator2-server/apks/appium-uiautomator2-server-debug-androidTest.apk'
2024-04-23 13:14:32:964 - [AndroidUiautomator2Driver@ba52 (b42df425)] Waiting up to 30000ms for UiAutomator2 to be online...
2024-04-23 13:14:32:977 - [AndroidUiautomator2Driver@ba52 (b42df425)] socket hang up
2024-04-23 13:14:33:983 - [AndroidUiautomator2Driver@ba52 (b42df425)] socket hang up
2024-04-23 13:14:33:991 - [HTTP] --> HEAD /wd/hub/status
2024-04-23 13:14:33:992 - [HTTP] {}
2024-04-23 13:14:33:992 - [HTTP] <-- HEAD /wd/hub/status 200 1 ms - 110
2024-04-23 13:14:33:992 - [HTTP] 
2024-04-23 13:14:34:934 - [HTTP] --> GET /wd/hub/status
2024-04-23 13:14:34:935 - [HTTP] {}
2024-04-23 13:14:34:937 - [HTTP] <-- GET /wd/hub/status 200 1 ms - 110
2024-04-23 13:14:34:937 - [HTTP] 
2024-04-23 13:14:35:008 - [AndroidUiautomator2Driver@ba52 (b42df425)] Determined the downstream protocol as 'W3C'
2024-04-23 13:14:35:060 - [AndroidUiautomator2Driver@ba52 (b42df425)] Screen already unlocked, doing nothing
2024-04-23 13:14:35:060 - [AndroidUiautomator2Driver@ba52 (b42df425)] Starting a chrome-based browser session
2024-04-23 13:14:35:136 - [Chromedriver@05d0] Set chromedriver binary as: /usr/lib/node_modules/appium/node_modules/appium-uiautomator2-driver/node_modules/appium-chromedriver/chromedriver/linux/chromedriver-linux64_v119.0.6045.105
2024-04-23 13:14:35:148 - [Chromedriver@05d0] No old chromedrivers seem to exist
2024-04-23 13:14:35:161 - [Chromedriver@05d0] Spawning chromedriver with: /usr/lib/node_modules/appium/node_modules/appium-uiautomator2-driver/node_modules/appium-chromedriver/chromedriver/linux/chromedriver-linux64_v119.0.6045.105 --port=36107 --adb-port=5037 --verbose
2024-04-23 13:14:35:174 - [Chromedriver@05d0] connect ECONNREFUSED 127.0.0.1:36107
2024-04-23 13:14:35:375 - [Chromedriver@05d0] Starting W3C Chromedriver session with capabilities: {
2024-04-23 13:14:35:375 - [Chromedriver@05d0]   "capabilities": {
2024-04-23 13:14:35:375 - [Chromedriver@05d0]     "alwaysMatch": {
2024-04-23 13:14:35:375 - [Chromedriver@05d0]       "goog:chromeOptions": {
2024-04-23 13:14:35:375 - [Chromedriver@05d0]         "androidPackage": "com.android.chrome",
2024-04-23 13:14:35:375 - [Chromedriver@05d0]         "androidDeviceSerial": "FA7371702902"
2024-04-23 13:14:35:375 - [Chromedriver@05d0]       },
2024-04-23 13:14:35:375 - [Chromedriver@05d0]       "goog:loggingPrefs": {
2024-04-23 13:14:35:375 - [Chromedriver@05d0]         "browser": "ALL"
2024-04-23 13:14:35:375 - [Chromedriver@05d0]       }
2024-04-23 13:14:35:375 - [Chromedriver@05d0]     }
2024-04-23 13:14:35:375 - [Chromedriver@05d0]   }
2024-04-23 13:14:35:376 - [Chromedriver@05d0] }
2024-04-23 13:14:35:379 - [Chromedriver@05d0] Got response with status 500: {"value":{"error":"unknown error","message":"unknown error: Failed to run adb command with networking error: net::ERR_ADDRESS_INVALID. Is the adb server running? Extra response: <>.","stacktrace":"#0 0x556500c235e3 <unknown>\n#1 0x5565008e60b7 <unknown>\n#2 0x5565008b1cff <unknown>\n#3 0x5565008afc2d <unknown>\n#4 0x5565008af41d <unknown>\n#5 0x5565008c4739 <unknown>\n#6 0x5565009188c2 <unknown>\n#7 0x55650096447f <unknown>\n#8 0x55650095acc3 <unknown>\n#9 0x5565009260e4 <unknown>\n#10 0x5565009270ae <unknown>\n#11 0x556500be9ce1 <unknown>\n#12 0x556500bedb7e <unknown>\n#13 0x556500bd74b5 <unknown>\n#14 0x556500bee7d6 <unknown>\n#15 0x556500bbadbf <unknown>\n#16 0x556500c11748 <unknown>\n#17 0x556500c11917 <unknown>\n#18 0x556500c22773 <unknown>\n#19 0x7feb0262f609 start_thread\n"}}
2024-04-23 13:14:35:381 - [Chromedriver@05d0] Chromedriver exited unexpectedly with code null, signal SIGTERM
2024-04-23 13:14:35:381 - [Chromedriver@05d0] An unknown server-side error occurred while processing the command. Original error: unknown error: Failed to run adb command with networking error: net::ERR_ADDRESS_INVALID. Is the adb server running? Extra response: <>.
2024-04-23 13:14:35:405 - [HTTP] <-- POST /wd/hub/session 500 7796 ms - 1114
2024-04-23 13:14:35:405 - [HTTP] 
2024-04-23 13:14:35:731 - [HTTP] --> GET /wd/hub/status-adb
2024-04-23 13:14:35:731 - [HTTP] {"exitCode":101}
2024-04-23 13:14:35:744 - [HTTP] <-- GET /wd/hub/status-adb 200 13 ms - 105
2024-04-23 13:14:35:744 - [HTTP] 
2024-04-23 13:14:35:787 - [HTTP] --> POST /wd/hub/session
2024-04-23 13:14:35:787 - [HTTP] {"desiredCapabilities":{"server:CONFIG_UUID":"775622f0-214a-4aba-b0ac-e79b422d4c04","appium:locale":"US","browserName":"chrome","zebrunner:slotCapabilities":{"deviceType":"TV","proxy_port":7443,"server:CONFIG_UUID":"775622f0-214a-4aba-b0ac-e79b422d4c04","seleniumProtocol":"WebDriver","server_proxy_port":7444,"adb_port":7442,"deviceName":"HTC_U_Ultra","platform":"ANDROID","platformVersion":"7.0","automationName":"uiautomator2","remoteURL":null,"maxInstances":1,"platformName":"android","udid":"FA7371702902"},"appium:language":"en","appium:remoteAppsCacheLimit":0,"appium:deviceName":"HTC_U_Ultra","platformName":"android","appium:automationName":"UIAutomator2","appium:app":"https://qaprosoft.s3-us-west-2.amazonaws.com/carinademoexample.apk"},"capabilities":{"firstMatch":[{"appium:app":"https://qaprosoft.s3-us-west-2.amazonaws.com/carinademoexample.apk","appium:automationName":"UIAutomator2","appium:deviceName":"HTC_U_Ultra","appium:language":"en","appium:locale":"US","appium:remoteAppsCacheLimit":0,"browserNam...
2024-04-23 13:14:35:788 - [Appium] Attempting to find matching driver for automationName 'UIAutomator2' and platformName 'android'
2024-04-23 13:14:35:788 - [Appium] The 'uiautomator2' driver was installed and matched caps.
2024-04-23 13:14:35:788 - [Appium] Will require it at /usr/lib/node_modules/appium/node_modules/appium-uiautomator2-driver
2024-04-23 13:14:35:788 - [AppiumDriver@7108] Appium v2.2.2 creating new AndroidUiautomator2Driver (v3.1.0) session
2024-04-23 13:14:35:788 - [AppiumDriver@7108] Checking BaseDriver versions for Appium and AndroidUiautomator2Driver
2024-04-23 13:14:35:788 - [AppiumDriver@7108] Appium's BaseDriver version is 9.4.3
2024-04-23 13:14:35:789 - [AppiumDriver@7108] AndroidUiautomator2Driver's BaseDriver version is 9.4.3
2024-04-23 13:14:35:791 - [AppiumDriver@7108] Applying relaxed security to 'AndroidUiautomator2Driver' as per server command line argument. All insecure features will be enabled unless explicitly disabled by --deny-insecure
2024-04-23 13:14:35:791 - [AppiumDriver@7108] Explicitly enabling use of insecure features:
2024-04-23 13:14:35:791 - [AppiumDriver@7108]     chromedriver_autodownload
2024-04-23 13:14:35:798 - [AndroidUiautomator2Driver@dbc9] The following provided capabilities were not recognized by this driver:
2024-04-23 13:14:35:799 - [AndroidUiautomator2Driver@dbc9]   server:CONFIG_UUID
2024-04-23 13:14:35:799 - [AndroidUiautomator2Driver@dbc9]   zebrunner:slotCapabilities
2024-04-23 13:14:35:799 - [AndroidUiautomator2Driver@dbc9] The desired capabilities should generally not include both an 'app' and a 'browserName'
2024-04-23 13:14:35:799 - [AndroidUiautomator2Driver@dbc9 (51abc82a)] Session created with session id: 51abc82a-7ed6-46a7-86c8-3e05eb89de3f
2024-04-23 13:14:35:800 - [ADB] Using 'adb' from '/opt/android/platform-tools/adb'
2024-04-23 13:14:35:816 - [AndroidUiautomator2Driver@dbc9 (51abc82a)] Retrieving device list
2024-04-23 13:14:35:832 - [AndroidUiautomator2Driver@dbc9 (51abc82a)] Using device: FA7371702902
2024-04-23 13:14:35:833 - [ADB] Using 'adb' from '/opt/android/platform-tools/adb'
2024-04-23 13:14:35:847 - [AndroidUiautomator2Driver@dbc9 (51abc82a)] We're going to run a Chrome-based session
2024-04-23 13:14:35:926 - [AndroidUiautomator2Driver@dbc9 (51abc82a)] Chrome-type package and activity are com.android.chrome and com.android.chrome/com.google.android.apps.chrome.Main
2024-04-23 13:14:35:926 - [BaseDriver] Using downloadable app 'https://qaprosoft.s3-us-west-2.amazonaws.com/carinademoexample.apk'
2024-04-23 13:14:36:744 - [BaseDriver] [MCLOUD] Target path [getLocalFileForAppUrl]: /opt/appium-storage/carinademoexample.apk
2024-04-23 13:14:36:745 - [BaseDriver] [MCLOUD] Local version of app was found. Will check actuality of the file
2024-04-23 13:14:37:355 - [BaseDriver] [MCLOUD] Remote file size is 9328742 and local file size is 9328742
2024-04-23 13:14:37:355 - [BaseDriver] [MCLOUD] Sizes are the same. Hence will use already stored application for the session
2024-04-23 13:14:37:393 - [AndroidUiautomator2Driver@dbc9 (51abc82a)] Capability 'appActivity' is expected to only include latin letters, digits, underscore, dot, comma and asterisk characters.
2024-04-23 13:14:37:393 - [AndroidUiautomator2Driver@dbc9 (51abc82a)] Current value 'com.android.chrome/com.google.android.apps.chrome.Main' has non-matching character at index 18: 'com.android.chrome/'
2024-04-23 13:14:37:889 - [AndroidUiautomator2Driver@dbc9 (51abc82a)] Performing fast reset on 'com.android.chrome'
2024-04-23 13:14:38:456 - [AndroidUiautomator2Driver@dbc9 (51abc82a)] Server packages are not going to be (re)installed
2024-04-23 13:14:38:993 - [ADB] Adding packages ["io.appium.settings","io.appium.uiautomator2.server","io.appium.uiautomator2.server.test"] to Doze whitelist
2024-04-23 13:14:39:938 - [HTTP] --> GET /wd/hub/status
2024-04-23 13:14:39:939 - [HTTP] {}
2024-04-23 13:14:39:940 - [HTTP] <-- GET /wd/hub/status 200 1 ms - 110
2024-04-23 13:14:39:940 - [HTTP] 
2024-04-23 13:14:40:315 - [AndroidUiautomator2Driver@dbc9 (51abc82a)] Starting UIAutomator2 server 7.0.5
2024-04-23 13:14:40:315 - [AndroidUiautomator2Driver@dbc9 (51abc82a)] Using UIAutomator2 server from '/usr/lib/node_modules/appium/node_modules/appium-uiautomator2-driver/node_modules/appium-uiautomator2-server/apks/appium-uiautomator2-server-v7.0.5.apk' and test from '/usr/lib/node_modules/appium/node_modules/appium-uiautomator2-driver/node_modules/appium-uiautomator2-server/apks/appium-uiautomator2-server-debug-androidTest.apk'
2024-04-23 13:14:40:315 - [AndroidUiautomator2Driver@dbc9 (51abc82a)] Waiting up to 30000ms for UiAutomator2 to be online...
2024-04-23 13:14:40:330 - [AndroidUiautomator2Driver@dbc9 (51abc82a)] socket hang up
2024-04-23 13:14:41:336 - [AndroidUiautomator2Driver@dbc9 (51abc82a)] socket hang up
2024-04-23 13:14:42:375 - [AndroidUiautomator2Driver@dbc9 (51abc82a)] Determined the downstream protocol as 'W3C'
2024-04-23 13:14:42:430 - [AndroidUiautomator2Driver@dbc9 (51abc82a)] Screen already unlocked, doing nothing
2024-04-23 13:14:42:431 - [AndroidUiautomator2Driver@dbc9 (51abc82a)] Starting a chrome-based browser session
2024-04-23 13:14:42:498 - [Chromedriver@b1f9] Set chromedriver binary as: /usr/lib/node_modules/appium/node_modules/appium-uiautomator2-driver/node_modules/appium-chromedriver/chromedriver/linux/chromedriver-linux64_v119.0.6045.105
2024-04-23 13:14:42:510 - [Chromedriver@b1f9] No old chromedrivers seem to exist
2024-04-23 13:14:42:521 - [Chromedriver@b1f9] Spawning chromedriver with: /usr/lib/node_modules/appium/node_modules/appium-uiautomator2-driver/node_modules/appium-chromedriver/chromedriver/linux/chromedriver-linux64_v119.0.6045.105 --port=36649 --adb-port=5037 --verbose
2024-04-23 13:14:42:533 - [Chromedriver@b1f9] connect ECONNREFUSED 127.0.0.1:36649
2024-04-23 13:14:42:736 - [Chromedriver@b1f9] Starting W3C Chromedriver session with capabilities: {
2024-04-23 13:14:42:736 - [Chromedriver@b1f9]   "capabilities": {
2024-04-23 13:14:42:736 - [Chromedriver@b1f9]     "alwaysMatch": {
2024-04-23 13:14:42:736 - [Chromedriver@b1f9]       "goog:chromeOptions": {
2024-04-23 13:14:42:736 - [Chromedriver@b1f9]         "androidPackage": "com.android.chrome",
2024-04-23 13:14:42:736 - [Chromedriver@b1f9]         "androidDeviceSerial": "FA7371702902"
2024-04-23 13:14:42:736 - [Chromedriver@b1f9]       },
2024-04-23 13:14:42:736 - [Chromedriver@b1f9]       "goog:loggingPrefs": {
2024-04-23 13:14:42:736 - [Chromedriver@b1f9]         "browser": "ALL"
2024-04-23 13:14:42:736 - [Chromedriver@b1f9]       }
2024-04-23 13:14:42:736 - [Chromedriver@b1f9]     }
2024-04-23 13:14:42:736 - [Chromedriver@b1f9]   }
2024-04-23 13:14:42:736 - [Chromedriver@b1f9] }
2024-04-23 13:14:42:739 - [Chromedriver@b1f9] Got response with status 500: {"value":{"error":"unknown error","message":"unknown error: Failed to run adb command with networking error: net::ERR_ADDRESS_INVALID. Is the adb server running? Extra response: <>.","stacktrace":"#0 0x556fcc9b85e3 <unknown>\n#1 0x556fcc67b0b7 <unknown>\n#2 0x556fcc646cff <unknown>\n#3 0x556fcc644c2d <unknown>\n#4 0x556fcc64441d <unknown>\n#5 0x556fcc659739 <unknown>\n#6 0x556fcc6ad8c2 <unknown>\n#7 0x556fcc6f947f <unknown>\n#8 0x556fcc6efcc3 <unknown>\n#9 0x556fcc6bb0e4 <unknown>\n#10 0x556fcc6bc0ae <unknown>\n#11 0x556fcc97ece1 <unknown>\n#12 0x556fcc982b7e <unknown>\n#13 0x556fcc96c4b5 <unknown>\n#14 0x556fcc9837d6 <unknown>\n#15 0x556fcc94fdbf <unknown>\n#16 0x556fcc9a6748 <unknown>\n#17 0x556fcc9a6917 <unknown>\n#18 0x556fcc9b7773 <unknown>\n#19 0x7fab08190609 start_thread\n"}}
2024-04-23 13:14:42:741 - [Chromedriver@b1f9] Chromedriver exited unexpectedly with code null, signal SIGTERM
2024-04-23 13:14:42:741 - [Chromedriver@b1f9] An unknown server-side error occurred while processing the command. Original error: unknown error: Failed to run adb command with networking error: net::ERR_ADDRESS_INVALID. Is the adb server running? Extra response: <>.
2024-04-23 13:14:42:767 - [HTTP] <-- POST /wd/hub/session 500 6981 ms - 1114
2024-04-23 13:14:42:768 - [HTTP] 
2024-04-23 13:14:42:886 - [HTTP] --> GET /wd/hub/status-adb
2024-04-23 13:14:42:886 - [HTTP] {"exitCode":101}
2024-04-23 13:14:42:901 - [HTTP] <-- GET /wd/hub/status-adb 200 15 ms - 105
2024-04-23 13:14:42:901 - [HTTP] 
2024-04-23 13:14:42:949 - [HTTP] --> POST /wd/hub/session
2024-04-23 13:14:42:949 - [HTTP] {"desiredCapabilities":{"server:CONFIG_UUID":"775622f0-214a-4aba-b0ac-e79b422d4c04","appium:locale":"US","browserName":"chrome","zebrunner:slotCapabilities":{"deviceType":"TV","proxy_port":7443,"server:CONFIG_UUID":"775622f0-214a-4aba-b0ac-e79b422d4c04","seleniumProtocol":"WebDriver","server_proxy_port":7444,"adb_port":7442,"deviceName":"HTC_U_Ultra","platform":"ANDROID","platformVersion":"7.0","automationName":"uiautomator2","remoteURL":null,"maxInstances":1,"platformName":"android","udid":"FA7371702902"},"appium:language":"en","appium:remoteAppsCacheLimit":0,"appium:deviceName":"HTC_U_Ultra","platformName":"android","appium:automationName":"UIAutomator2","appium:app":"https://qaprosoft.s3-us-west-2.amazonaws.com/carinademoexample.apk"},"capabilities":{"firstMatch":[{"appium:app":"https://qaprosoft.s3-us-west-2.amazonaws.com/carinademoexample.apk","appium:automationName":"UIAutomator2","appium:deviceName":"HTC_U_Ultra","appium:language":"en","appium:locale":"US","appium:remoteAppsCacheLimit":0,"browserNam...
2024-04-23 13:14:42:950 - [Appium] Attempting to find matching driver for automationName 'UIAutomator2' and platformName 'android'
2024-04-23 13:14:42:950 - [Appium] The 'uiautomator2' driver was installed and matched caps.
2024-04-23 13:14:42:950 - [Appium] Will require it at /usr/lib/node_modules/appium/node_modules/appium-uiautomator2-driver
2024-04-23 13:14:42:950 - [AppiumDriver@7108] Appium v2.2.2 creating new AndroidUiautomator2Driver (v3.1.0) session
2024-04-23 13:14:42:950 - [AppiumDriver@7108] Checking BaseDriver versions for Appium and AndroidUiautomator2Driver
2024-04-23 13:14:42:950 - [AppiumDriver@7108] Appium's BaseDriver version is 9.4.3
2024-04-23 13:14:42:950 - [AppiumDriver@7108] AndroidUiautomator2Driver's BaseDriver version is 9.4.3
2024-04-23 13:14:42:952 - [AppiumDriver@7108] Applying relaxed security to 'AndroidUiautomator2Driver' as per server command line argument. All insecure features will be enabled unless explicitly disabled by --deny-insecure
2024-04-23 13:14:42:952 - [AppiumDriver@7108] Explicitly enabling use of insecure features:
2024-04-23 13:14:42:952 - [AppiumDriver@7108]     chromedriver_autodownload
2024-04-23 13:14:42:958 - [AndroidUiautomator2Driver@1b16] The following provided capabilities were not recognized by this driver:
2024-04-23 13:14:42:958 - [AndroidUiautomator2Driver@1b16]   server:CONFIG_UUID
2024-04-23 13:14:42:958 - [AndroidUiautomator2Driver@1b16]   zebrunner:slotCapabilities
2024-04-23 13:14:42:958 - [AndroidUiautomator2Driver@1b16] The desired capabilities should generally not include both an 'app' and a 'browserName'
2024-04-23 13:14:42:958 - [AndroidUiautomator2Driver@1b16 (054aae93)] Session created with session id: 054aae93-62c7-489a-a9a8-f294edb22b31
2024-04-23 13:14:42:959 - [ADB] Using 'adb' from '/opt/android/platform-tools/adb'
2024-04-23 13:14:42:971 - [AndroidUiautomator2Driver@1b16 (054aae93)] Retrieving device list
2024-04-23 13:14:42:983 - [AndroidUiautomator2Driver@1b16 (054aae93)] Using device: FA7371702902
2024-04-23 13:14:42:983 - [ADB] Using 'adb' from '/opt/android/platform-tools/adb'
2024-04-23 13:14:42:994 - [AndroidUiautomator2Driver@1b16 (054aae93)] We're going to run a Chrome-based session
2024-04-23 13:14:43:059 - [AndroidUiautomator2Driver@1b16 (054aae93)] Chrome-type package and activity are com.android.chrome and com.android.chrome/com.google.android.apps.chrome.Main
2024-04-23 13:14:43:060 - [BaseDriver] Using downloadable app 'https://qaprosoft.s3-us-west-2.amazonaws.com/carinademoexample.apk'
2024-04-23 13:14:43:664 - [BaseDriver] [MCLOUD] Target path [getLocalFileForAppUrl]: /opt/appium-storage/carinademoexample.apk
2024-04-23 13:14:43:665 - [BaseDriver] [MCLOUD] Local version of app was found. Will check actuality of the file
2024-04-23 13:14:44:087 - [HTTP] --> HEAD /wd/hub/status
2024-04-23 13:14:44:087 - [HTTP] {}
2024-04-23 13:14:44:087 - [HTTP] <-- HEAD /wd/hub/status 200 1 ms - 110
2024-04-23 13:14:44:087 - [HTTP] 
2024-04-23 13:14:44:240 - [BaseDriver] [MCLOUD] Remote file size is 9328742 and local file size is 9328742
2024-04-23 13:14:44:241 - [BaseDriver] [MCLOUD] Sizes are the same. Hence will use already stored application for the session
2024-04-23 13:14:44:283 - [AndroidUiautomator2Driver@1b16 (054aae93)] Capability 'appActivity' is expected to only include latin letters, digits, underscore, dot, comma and asterisk characters.
2024-04-23 13:14:44:283 - [AndroidUiautomator2Driver@1b16 (054aae93)] Current value 'com.android.chrome/com.google.android.apps.chrome.Main' has non-matching character at index 18: 'com.android.chrome/'
2024-04-23 13:14:44:755 - [AndroidUiautomator2Driver@1b16 (054aae93)] Performing fast reset on 'com.android.chrome'
2024-04-23 13:14:44:941 - [HTTP] --> GET /wd/hub/status
2024-04-23 13:14:44:941 - [HTTP] {}
2024-04-23 13:14:44:942 - [HTTP] <-- GET /wd/hub/status 200 1 ms - 110
2024-04-23 13:14:44:942 - [HTTP] 
2024-04-23 13:14:45:135 - [AndroidUiautomator2Driver@1b16 (054aae93)] Server packages are not going to be (re)installed
2024-04-23 13:14:45:705 - [ADB] Adding packages ["io.appium.settings","io.appium.uiautomator2.server","io.appium.uiautomator2.server.test"] to Doze whitelist
2024-04-23 13:14:47:281 - [AndroidUiautomator2Driver@1b16 (054aae93)] Starting UIAutomator2 server 7.0.5
2024-04-23 13:14:47:281 - [AndroidUiautomator2Driver@1b16 (054aae93)] Using UIAutomator2 server from '/usr/lib/node_modules/appium/node_modules/appium-uiautomator2-driver/node_modules/appium-uiautomator2-server/apks/appium-uiautomator2-server-v7.0.5.apk' and test from '/usr/lib/node_modules/appium/node_modules/appium-uiautomator2-driver/node_modules/appium-uiautomator2-server/apks/appium-uiautomator2-server-debug-androidTest.apk'
2024-04-23 13:14:47:282 - [AndroidUiautomator2Driver@1b16 (054aae93)] Waiting up to 30000ms for UiAutomator2 to be online...
2024-04-23 13:14:47:295 - [AndroidUiautomator2Driver@1b16 (054aae93)] socket hang up
2024-04-23 13:14:48:300 - [AndroidUiautomator2Driver@1b16 (054aae93)] socket hang up
2024-04-23 13:14:49:339 - [AndroidUiautomator2Driver@1b16 (054aae93)] Determined the downstream protocol as 'W3C'
2024-04-23 13:14:49:398 - [AndroidUiautomator2Driver@1b16 (054aae93)] Screen already unlocked, doing nothing
2024-04-23 13:14:49:398 - [AndroidUiautomator2Driver@1b16 (054aae93)] Starting a chrome-based browser session
2024-04-23 13:14:49:464 - [Chromedriver@d3d6] Set chromedriver binary as: /usr/lib/node_modules/appium/node_modules/appium-uiautomator2-driver/node_modules/appium-chromedriver/chromedriver/linux/chromedriver-linux64_v119.0.6045.105
2024-04-23 13:14:49:477 - [Chromedriver@d3d6] No old chromedrivers seem to exist
2024-04-23 13:14:49:489 - [Chromedriver@d3d6] Spawning chromedriver with: /usr/lib/node_modules/appium/node_modules/appium-uiautomator2-driver/node_modules/appium-chromedriver/chromedriver/linux/chromedriver-linux64_v119.0.6045.105 --port=46401 --adb-port=5037 --verbose
2024-04-23 13:14:49:501 - [Chromedriver@d3d6] connect ECONNREFUSED 127.0.0.1:46401
2024-04-23 13:14:49:703 - [Chromedriver@d3d6] Starting W3C Chromedriver session with capabilities: {
2024-04-23 13:14:49:703 - [Chromedriver@d3d6]   "capabilities": {
2024-04-23 13:14:49:703 - [Chromedriver@d3d6]     "alwaysMatch": {
2024-04-23 13:14:49:703 - [Chromedriver@d3d6]       "goog:chromeOptions": {
2024-04-23 13:14:49:703 - [Chromedriver@d3d6]         "androidPackage": "com.android.chrome",
2024-04-23 13:14:49:703 - [Chromedriver@d3d6]         "androidDeviceSerial": "FA7371702902"
2024-04-23 13:14:49:703 - [Chromedriver@d3d6]       },
2024-04-23 13:14:49:703 - [Chromedriver@d3d6]       "goog:loggingPrefs": {
2024-04-23 13:14:49:703 - [Chromedriver@d3d6]         "browser": "ALL"
2024-04-23 13:14:49:703 - [Chromedriver@d3d6]       }
2024-04-23 13:14:49:704 - [Chromedriver@d3d6]     }
2024-04-23 13:14:49:704 - [Chromedriver@d3d6]   }
2024-04-23 13:14:49:704 - [Chromedriver@d3d6] }
2024-04-23 13:14:49:707 - [Chromedriver@d3d6] Got response with status 500: {"value":{"error":"unknown error","message":"unknown error: Failed to run adb command with networking error: net::ERR_ADDRESS_INVALID. Is the adb server running? Extra response: <>.","stacktrace":"#0 0x55dbfeb715e3 <unknown>\n#1 0x55dbfe8340b7 <unknown>\n#2 0x55dbfe7ffcff <unknown>\n#3 0x55dbfe7fdc2d <unknown>\n#4 0x55dbfe7fd41d <unknown>\n#5 0x55dbfe812739 <unknown>\n#6 0x55dbfe8668c2 <unknown>\n#7 0x55dbfe8b247f <unknown>\n#8 0x55dbfe8a8cc3 <unknown>\n#9 0x55dbfe8740e4 <unknown>\n#10 0x55dbfe8750ae <unknown>\n#11 0x55dbfeb37ce1 <unknown>\n#12 0x55dbfeb3bb7e <unknown>\n#13 0x55dbfeb254b5 <unknown>\n#14 0x55dbfeb3c7d6 <unknown>\n#15 0x55dbfeb08dbf <unknown>\n#16 0x55dbfeb5f748 <unknown>\n#17 0x55dbfeb5f917 <unknown>\n#18 0x55dbfeb70773 <unknown>\n#19 0x7f23322ae609 start_thread\n"}}
2024-04-23 13:14:49:708 - [Chromedriver@d3d6] Chromedriver exited unexpectedly with code null, signal SIGTERM
2024-04-23 13:14:49:709 - [Chromedriver@d3d6] An unknown server-side error occurred while processing the command. Original error: unknown error: Failed to run adb command with networking error: net::ERR_ADDRESS_INVALID. Is the adb server running? Extra response: <>.
2024-04-23 13:14:49:739 - [HTTP] <-- POST /wd/hub/session 500 6789 ms - 1114
2024-04-23 13:14:49:739 - [HTTP] 
2024-04-23 13:14:49:944 - [HTTP] --> GET /wd/hub/status
2024-04-23 13:14:49:945 - [HTTP] {}
2024-04-23 13:14:49:946 - [HTTP] <-- GET /wd/hub/status 200 1 ms - 110
vdelendik commented 5 months ago

actual issue is for mobile web tests...

azarouski commented 4 months ago

fixed

387

dhreben commented 4 months ago

Fixed