CTS_ERROR >>> Failed to execute shell command am instrument - cts

Using the Android 2.2, API-8, SDK-r7 along with CTS-2.2_r4 suite.
Updated the SDK_ROOT environment variable with SDK_r7 tools in “android-cts/tools/startcts” script and the “SDK_ROOT/tools” also included in PATH environment variable.
Ran the “android” and created a new virtual device and started the same. This invokes the emulator named as “emulator-5554”.
Now, started the cts using the below command:
bash android-cts/tools/startcts.
start –plan android
Above command failed with:
Test package: android.app
install met failure [install_failed_insufficient_storage]
CTS_ERROR >>> Failed to execute shell command am instrument -w -r -e package android com.android.cts.app/android.test.InstrumentationCtsTestRunner on device emulator-5554
com.android.ddmlib.ShellCommandUnresponsiveException.
A few more issues are:
CTS_ERROR >>> Got exception while processing command
CTS_ERROR >>> Installing met timeout due to Unknown reason
CTS_ERROR >>> Timeout: ReferenceAppTest
CTS_ERROR >>> Timeout: getDeviceInfo
Any hint to avoid the above timeout issues? Thank you very much for anticipating a quick response from you.

I did not got this error on the CTS 2.1 r5. But I am not running the SDK test that Android but my own tests instead. There for I will use the CTS 2.1 for a while.

Related

Getting this error when running ng e2e on mac with visual studio code

Setup :
#angular/cli#8.1.2
#ionic/cli#6.12.3
cordova#10.0.0
npm#6.14.10
“protractor”: “~5.4.0
Mac OS : Catalina
This is the error I am getting
** Angular Live Development Server is listening on localhost:4200, open your browser on http://localhost:4200/ **
:information_source: 「wdm」: Compiled successfully.
[12:08:58] I/launcher - Running 1 instances of WebDriver
[12:08:58] I/direct - Using ChromeDriver directly...
[12:08:58] E/runner - Unable to start a WebDriver session.
[12:08:58] E/launcher - Error: Error: spawn Unknown system error -86
at ChildProcess.spawn (internal/child_process.js:403:11)
at Object.spawn (child_process.js:553:9)
at exec (/Users/sunilharan/Documents/Projects/IONIC/App_NAME/node_modules/selenium-webdriver/io/exec.js:116:27)
at /Users/sunilharan/Documents/Projects/IONIC/App_NAME/node_modules/selenium-webdriver/remote/index.js:219:25
at processTicksAndRejections (internal/process/task_queues.js:93:5)
[12:08:58] E/launcher - Process exited with error code 100
This same setup is working on another machine running on M1 chip. I have tried on different computers but not working on any of them except my M1 Macbook Pro.
This is an issue with the latest chromedriver on MacOS. Please see detailed resolutions in this ticket.
"As a general solution, simply avoid using the chromedriver that has _m1 in its filename if you are on an Intel mac."
OSX fix Selenium Chromedriver launch error spawn Unknown system error -86 Bad CPU type in executable?

Getting INSTALL_FAILED_UPDATE_INCOMPATIBLE error

Appium Server version: 1.7.1
OS: Windows 8
While running the code I got
org.openqa.selenium.WebDriverException:
An unknown server-side error occurred while processing the command.
Original error:
Error executing adbExec.
Original error:
'Command 'D\:\\Android\\android-sdk\\platform-tools\\adb.exe -P 8080 -s ------ install C\:\\Users\\resi\\AppData\\Local\\Programs\\appium-desktop\\resources\\app\\node_modules\\appium\\node_modules\\appium-unlock \\bin\\unlock_apk-debug.apk' exited with code 1';
Stderr: 'Failed to install C:\Users\resi\AppData\Local\Programs\appium-desktop \resources\app\node_modules\appium\node_modules\appium-unlock\bin\unlock_apk-debug.apk:
Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE:
Package io.appium.unlock signatures do not match the previously installed version; ignoring!]'; Code: '1'
error and Appium Setting page is opened and instant closed in real Android device instead of opening app (.apk file)
You need to cleanup the device you are using:
Go to Settings -> Apps
Delete you application under test using Uninstall for all users menu
Delete Appium Settings app
Restart your test and it should work

Swift Perfect Docker Debugging the build process

I am woking on Swift Perfect server programming. My code is compiling on MacOS successfully and able to run on localhost. But, when I try with Linux build in Perfect Assistant, it is giving following error
unable to execute command: Killed
<unknown>:0: error: compile command failed due to signal (use -v to see invocation)
Failed: systemError(1, "sh: no job control in this shell\n<unknown>:0: error: build had 1 command failures\nswift-build: error: exit(1): /swift-3.0.2-RELEASE-ubuntu16.04/usr/bin/swift-build-tool -f /perfectbuild/.build_lin/release.yaml\n")
Tired of figuring out where the problem is and how to debug it. I'm new to docker as well. Please guide me regarding this.
When I try making linux executable I'm getting the following error
docker: Error response from daemon: oci runtime error: container_linux.go:247: starting container process caused "exec: \".build_lin/debug/S-server\": stat .build_lin/debug/S-server: no such file or directory".

Ionic run on device not working - daemon issue

It was working find, however now I'm getting the below error, when I run this command:
ionic run android
ERROR running one or more of the platforms: Error: adb: Command failed with exit code 1 Error output:
adb I 3000 58815 usb_osx.cpp:259] Found vid=04e8 pid=6860 serial=41007659c88da12f
adb I 3000 58815 usb_osx.cpp:259]
error: could not install smartsocket listener: Address already in use
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
You may not have the required environment or OS to run this project

Running appium with command line from eclipse : Could not initialize ideviceinstaller

First post.
Hi, I'm trying to run appium by executing the following command lines from eclipse:
Process pr = rt.exec(new String[] {"/usr/local/bin/node", "/usr/local/bin/appium"});
And then I run an AppiumDriver with the url and it's capabilities (also from eclipse): AppiumDriver ad = new AppiumDriver(new URL(url), this.capabilities);
These errors follow:
[36minfo[39m: [debug] Dynamic bootstrap path:
/Users/philippe.pageau/Library/Application
Support/appium/bootstrap/bootstrap-072528be314c3cc6.js
[36minfo[39m:
[debug] Reusing dynamic bootstrap:
/Users/philippe.pageau/Library/Application
Support/appium/bootstrap/bootstrap-072528be314c3cc6.js
[36minfo[39m:
[debug] Attempting iOS device log capture via libimobiledevice
idevicesyslog
[33mwarn[39m: Could not capture device log using
libimobiledevice idevicesyslog. Libimobiledevice probably isn't
installed
[36minfo[39m: [debug] Attempting iOS device log capture
via deviceconsole
[33mwarn[39m: Could not capture logs from device.
Continuing without capturing logs.
[36minfo[39m: [debug] Creating iDevice object with udid XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
[36minfo[39m: [debug] Couldn't find ideviceinstaller, trying
built-in at
/usr/local/lib/node_modules/appium/build/libimobiledevice-macosx/ideviceinstaller
[36minfo[39m: [debug] Cleaning up appium session [36minfo[39m:
[debug] Error: Could not initialize ideviceinstaller; make sure it is
installed and works on your system
at [object Object].IOS.getIDeviceObj (/usr/local/lib/node_modules/appium/lib/devices/ios/ios.js:909:13)
at [object Object].IOS.installToRealDevice (/usr/local/lib/node_modules/appium/lib/devices/ios/ios.js:856:32)
at /usr/local/lib/node_modules/appium/node_modules/async/lib/async.js:607:21
at /usr/local/lib/node_modules/appium/node_modules/async/lib/async.js:246:17
at iterate (/usr/local/lib/node_modules/appium/node_modules/async/lib/async.js:146:13)
at /usr/local/lib/node_modules/appium/node_modules/async/lib/async.js:157:25
at /usr/local/lib/node_modules/appium/node_modules/async/lib/async.js:248:21
at /usr/local/lib/node_modules/appium/node_modules/async/lib/async.js:612:34
at [object Object]. (/usr/local/lib/node_modules/appium/lib/devices/ios/ios.js:1527:14)
at /usr/local/lib/node_modules/appium/node_modules/underscore/underscore.js:890:21
at [object Object]._onTimeout (/usr/local/lib/node_modules/appium/lib/devices/ios/ios-log.js:166:7)
at Timer.listOnTimeout (timers.js:110:15)
[36minfo[39m: [debug] Responding to client with error: {"status":33,"value":{"message":"A
new session could not be created. (Original error: Could not
initialize ideviceinstaller; make sure it is installed and works on
your system)","origValue":"Could not initialize ideviceinstaller; make
sure it is installed and works on your system"},"sessionId":null}
[36minfo[39m: [37m<-- POST /wd/hub/session [39m[31m500[39m[90m
11133.802 ms - 300[39m [90m[39m
Exception in thread "main" org.openqa.selenium.SessionNotCreatedException: A new session could
not be created. (Original error: Could not initialize
ideviceinstaller; make sure it is installed and works on your system)
(WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 11.35 seconds
The errors show that it didn't find ideviceinstaller nor libimobiledevice (which I both installed)
I followed these instructions
Appium throws "ideviceinstaller" not found when launched through Eclipse - Java
http://technotesonthego.blogspot.ca/2013/10/install-libimobiledevice-on-mac-os-x.html
Note that I wish to execute everything from eclipse, allowing the QA to not worry about those things. It works with the GUI (I uninstalled it afterwards) and it also works when I run appium in the terminal and execute AppiumDriver ad = new AppiumDriver(new URL(url), this.capabilities); with eclipse.
I did my research, and asking the question to stackoverflow is my last resort.
Did I miss something?
EDIT
Also, I tried executing /usr/local/lib/node_modules/appium/build/libimobiledevice-macosx/ideviceinstall‌​er and it gave me this error : dyld: Library not loaded: #executable_path/../lib/libimobiledevice.3.dylib Referenced from: /usr/local/lib/node_modules/appium/build/libimobiledevice-macosx/ideviceinstalle‌​r Reason: image not found Trace/BPT trap: 5
Tried on Appium 1.4.8:
Step 1: install the "brew" command
Step 2: run the following command: brew install --HEAD ideviceinstaller
Step 3 (optional): click Appium/Reset Preferences and then close & open Appium
Good luck.