New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Appium : Can we run test cases on multiple device/Simulator from the same machine ? #3637

Closed
sesudhanshu opened this Issue Sep 15, 2014 · 74 comments

Comments

Projects
None yet
@sesudhanshu

sesudhanshu commented Sep 15, 2014

No description provided.

@sesudhanshu

This comment has been minimized.

Show comment
Hide comment
@sesudhanshu

sesudhanshu Sep 15, 2014

Hi All,

Can we connect multiple devices on the same machine and run our tests cases on it parallel ?
Is it possible to start multiple sessions of Appium on different ports ?

Then how and which test send requests to which port ?

sesudhanshu commented Sep 15, 2014

Hi All,

Can we connect multiple devices on the same machine and run our tests cases on it parallel ?
Is it possible to start multiple sessions of Appium on different ports ?

Then how and which test send requests to which port ?

@curtissiemens

This comment has been minimized.

Show comment
Hide comment
@curtissiemens

curtissiemens Sep 15, 2014

Contributor

For testing Android devices this is possible. We've even done research and if you host on a Linux machine there is a command to restart a single USB port - because sometimes certain devices (especially Samsung) just quit communicating.

For testing iOS it is possible to do this if you spin up 2+ VMs on a OS-X host. There is some configuration work to send one device to first VM and the second device to the second VM.

Contributor

curtissiemens commented Sep 15, 2014

For testing Android devices this is possible. We've even done research and if you host on a Linux machine there is a command to restart a single USB port - because sometimes certain devices (especially Samsung) just quit communicating.

For testing iOS it is possible to do this if you spin up 2+ VMs on a OS-X host. There is some configuration work to send one device to first VM and the second device to the second VM.

@bootstraponline

This comment has been minimized.

Show comment
Hide comment
@bootstraponline

bootstraponline Sep 15, 2014

Member

because sometimes certain devices (especially Samsung) just quit communicating.

I've seen this as well.

Member

bootstraponline commented Sep 15, 2014

because sometimes certain devices (especially Samsung) just quit communicating.

I've seen this as well.

@curtissiemens

This comment has been minimized.

Show comment
Hide comment
@curtissiemens

curtissiemens Sep 15, 2014

Contributor

We run these 2 commands to unbind & rebind the port that is associated with the device that isn't communicating. I.e. if we do "adb devices" and we don't see the device we want among the device list then we unbind/bind the associated usb port.
echo 'usb_port' | sudo tee /sys/bus/usb/drivers/usb/unbind"
echo 'usb_port' | sudo tee /sys/bus/usb/drivers/usb/bind"

This we don't have to do adb kill_server - because that kills the communication with all devices so if other devices had a test-case running you would have just caused a false failure (and good luck tracking that kind of sporadic thing down).

Contributor

curtissiemens commented Sep 15, 2014

We run these 2 commands to unbind & rebind the port that is associated with the device that isn't communicating. I.e. if we do "adb devices" and we don't see the device we want among the device list then we unbind/bind the associated usb port.
echo 'usb_port' | sudo tee /sys/bus/usb/drivers/usb/unbind"
echo 'usb_port' | sudo tee /sys/bus/usb/drivers/usb/bind"

This we don't have to do adb kill_server - because that kills the communication with all devices so if other devices had a test-case running you would have just caused a false failure (and good luck tracking that kind of sporadic thing down).

@bootstraponline

This comment has been minimized.

Show comment
Hide comment
@bootstraponline

bootstraponline Sep 15, 2014

Member

Thanks for the details. We should probably add this to the physical device documentation.

Member

bootstraponline commented Sep 15, 2014

Thanks for the details. We should probably add this to the physical device documentation.

@0x1mason

This comment has been minimized.

Show comment
Hide comment
@0x1mason

0x1mason Sep 15, 2014

The iOS simulator instance restriction is per user session rather than per machine. You can run as many simulator instances as you have user accounts. Each instance has to run in a sep account, obviously, but it's not difficult to manage those instances from a single account.

0x1mason commented Sep 15, 2014

The iOS simulator instance restriction is per user session rather than per machine. You can run as many simulator instances as you have user accounts. Each instance has to run in a sep account, obviously, but it's not difficult to manage those instances from a single account.

@priyankshah217

This comment has been minimized.

Show comment
Hide comment
@priyankshah217

priyankshah217 Sep 16, 2014

This possible in case of android only.

  • Launch multiple appium server instances with different port bindings (port,bootstrap port or selendroid port,device id)

priyankshah217 commented Sep 16, 2014

This possible in case of android only.

  • Launch multiple appium server instances with different port bindings (port,bootstrap port or selendroid port,device id)
@esimeonov

This comment has been minimized.

Show comment
Hide comment
@esimeonov

esimeonov Sep 16, 2014

@0x1mason How do you manage to start appium to test iOS apps with different users simultaneously? I can't do this with Appium 1.2.2, for example. Is anything required in terms of system configuration or Appium configuration?

esimeonov commented Sep 16, 2014

@0x1mason How do you manage to start appium to test iOS apps with different users simultaneously? I can't do this with Appium 1.2.2, for example. Is anything required in terms of system configuration or Appium configuration?

@0x1mason

This comment has been minimized.

Show comment
Hide comment
@0x1mason

0x1mason Sep 16, 2014

@esimeonov You can't do it with Appium alone, atm. Think of each user session as a separate machine. You'd use the same mechanisms to run tests in the user sessions as you would to run tests on VMs as curtissiemens describes.

0x1mason commented Sep 16, 2014

@esimeonov You can't do it with Appium alone, atm. Think of each user session as a separate machine. You'd use the same mechanisms to run tests in the user sessions as you would to run tests on VMs as curtissiemens describes.

@curtissiemens

This comment has been minimized.

Show comment
Hide comment
@curtissiemens

curtissiemens Sep 16, 2014

Contributor

I once tested 2 use accounts on a Mac, each to drive their own iOS Simulators (so I could get 2 Simulator test-cases running in parallel) - each running on different appium ports. It still didn't work. I remember there is a conflict with the Instruments port - something I couldn't configure.
In the end we concluded that for iOS you have to have VMs on the Mac - i.e. only 1 instruments run per OS.

For Android instruments isn't involved and you can just start appium on different ports and run in parallel. Never have tried this on a Mac - but it would probably work. We've done it on a Linux machine using a single user login running against multiple Android devices. I think its even possible to run against multiple Android Emulators on the same login/screen - although you have to be careful to have all the Emulators run on different ports.

Contributor

curtissiemens commented Sep 16, 2014

I once tested 2 use accounts on a Mac, each to drive their own iOS Simulators (so I could get 2 Simulator test-cases running in parallel) - each running on different appium ports. It still didn't work. I remember there is a conflict with the Instruments port - something I couldn't configure.
In the end we concluded that for iOS you have to have VMs on the Mac - i.e. only 1 instruments run per OS.

For Android instruments isn't involved and you can just start appium on different ports and run in parallel. Never have tried this on a Mac - but it would probably work. We've done it on a Linux machine using a single user login running against multiple Android devices. I think its even possible to run against multiple Android Emulators on the same login/screen - although you have to be careful to have all the Emulators run on different ports.

@0x1mason

This comment has been minimized.

Show comment
Hide comment
@0x1mason

0x1mason Sep 16, 2014

I'll take another look at it. Maybe I made a mistake in my testing.

0x1mason commented Sep 16, 2014

I'll take another look at it. Maybe I made a mistake in my testing.

@Hassan-Radi

This comment has been minimized.

Show comment
Hide comment
@Hassan-Radi

Hassan-Radi Sep 17, 2014

You can achieve it on Android by following this: #3592 (comment)

Hassan-Radi commented Sep 17, 2014

You can achieve it on Android by following this: #3592 (comment)

@sebv

This comment has been minimized.

Show comment
Hide comment
@sebv

sebv Nov 2, 2014

Member

With the current version of Appium you will need several instances. Please use the discussion group to exchange information on this topic.

I've made a note so we look at it (much) later we have other priorities for now. #3950

Member

sebv commented Nov 2, 2014

With the current version of Appium you will need several instances. Please use the discussion group to exchange information on this topic.

I've made a note so we look at it (much) later we have other priorities for now. #3950

@sebv sebv closed this Nov 2, 2014

@sebv sebv removed the NeedsTriage label Nov 2, 2014

@sebv sebv removed their assignment Nov 2, 2014

@p00j4

This comment has been minimized.

Show comment
Hide comment
@p00j4

p00j4 Dec 31, 2014

I hear that ios parallel test is not possible, however can we execute an android and an ios test in parallel on same machine ? [or 1 ios test on simulator and another on ios device ?]

p00j4 commented Dec 31, 2014

I hear that ios parallel test is not possible, however can we execute an android and an ios test in parallel on same machine ? [or 1 ios test on simulator and another on ios device ?]

@p00j4

This comment has been minimized.

Show comment
Hide comment
@p00j4

p00j4 Dec 31, 2014

@bootstraponline : what do you say !

p00j4 commented Dec 31, 2014

@bootstraponline : what do you say !

@saikrishna321

This comment has been minimized.

Show comment
Hide comment
@saikrishna321

saikrishna321 Dec 31, 2014

Member

@p00j4 [ or 1 ios test on simulator and another on ios device ?] even this not possible as simulator and device the Instruments in hood. ..

Member

saikrishna321 commented Dec 31, 2014

@p00j4 [ or 1 ios test on simulator and another on ios device ?] even this not possible as simulator and device the Instruments in hood. ..

@p00j4

This comment has been minimized.

Show comment
Hide comment
@p00j4

p00j4 Dec 31, 2014

hmm, right @saikrishna321 , thanks for reply.
but an android and an ios test in parallel on same machine should work, isn't it ?
I could have try and figure out but stuck @ this issue #3592 (comment)

p00j4 commented Dec 31, 2014

hmm, right @saikrishna321 , thanks for reply.
but an android and an ios test in parallel on same machine should work, isn't it ?
I could have try and figure out but stuck @ this issue #3592 (comment)

@saikrishna321

This comment has been minimized.

Show comment
Hide comment
@saikrishna321

saikrishna321 Dec 31, 2014

Member

@p00j4 yah an android and an ios test in parallel on same machine should work. As per @curtissiemens comment above yes we need to have 1 instruments for 1 iDevice so we as well ended up with VM's

Member

saikrishna321 commented Dec 31, 2014

@p00j4 yah an android and an ios test in parallel on same machine should work. As per @curtissiemens comment above yes we need to have 1 instruments for 1 iDevice so we as well ended up with VM's

@curtissiemens

This comment has been minimized.

Show comment
Hide comment
@curtissiemens

curtissiemens Dec 31, 2014

Contributor

Never tried an iOS Simulator and an Android Device both running at the same time off of a Mac.
It would probably work - just make sure to startup the appium server on different ports (like 10 higher than the first one) I.e. startup the first appium server on 4723 (default port) and then the second on 4733.

Note: You can run multiple Android Devices off of a Linux machine and therefore trying to make your Mac machines "go farther" is not required. Linux machines are cheaper than Macs and don't have all the permission (setup) issues that Mac has in running Appium.
Also, some Android devices (especially Samsung) just disconnect and you don't want to adb kill-server adb start-server to reconnect because that will kill all of the connects to all android devices and destroy all the parallel running testcases.
Instead on Linux you can reconnect a android device by doing these 2 commands (using the appropriate device port):
echo 4725 | sudo tee /sys/bus/usb/drivers/usb/unbind
echo 4725 | sudo tee /sys/bus/usb/drivers/usb/bind
The unbind & bind commands do not exist on Mac so you really need Linux to run multiple Appium testcases (on parallel android devices) from a single hosting machine.

Contributor

curtissiemens commented Dec 31, 2014

Never tried an iOS Simulator and an Android Device both running at the same time off of a Mac.
It would probably work - just make sure to startup the appium server on different ports (like 10 higher than the first one) I.e. startup the first appium server on 4723 (default port) and then the second on 4733.

Note: You can run multiple Android Devices off of a Linux machine and therefore trying to make your Mac machines "go farther" is not required. Linux machines are cheaper than Macs and don't have all the permission (setup) issues that Mac has in running Appium.
Also, some Android devices (especially Samsung) just disconnect and you don't want to adb kill-server adb start-server to reconnect because that will kill all of the connects to all android devices and destroy all the parallel running testcases.
Instead on Linux you can reconnect a android device by doing these 2 commands (using the appropriate device port):
echo 4725 | sudo tee /sys/bus/usb/drivers/usb/unbind
echo 4725 | sudo tee /sys/bus/usb/drivers/usb/bind
The unbind & bind commands do not exist on Mac so you really need Linux to run multiple Appium testcases (on parallel android devices) from a single hosting machine.

@p00j4

This comment has been minimized.

Show comment
Hide comment
@p00j4

p00j4 Jan 1, 2015

@curtissiemens : thanks for detailed reply. As per my current requirement, I want to utilise 1 resource for both app testing (Android, IOS), and for that 1-1 device is fine, thats the reason I'm looking for running both on same machine (MAC), but I dnt know why I'm not able to execute even on a single device after changing the port , here is the log:#3592 (comment), it looks like some setting issue, any idea to solve this !

p00j4 commented Jan 1, 2015

@curtissiemens : thanks for detailed reply. As per my current requirement, I want to utilise 1 resource for both app testing (Android, IOS), and for that 1-1 device is fine, thats the reason I'm looking for running both on same machine (MAC), but I dnt know why I'm not able to execute even on a single device after changing the port , here is the log:#3592 (comment), it looks like some setting issue, any idea to solve this !

@shady333

This comment has been minimized.

Show comment
Hide comment
@shady333

shady333 Nov 25, 2015

we are on appium 1.3.7 and xcode 7
25 лист. 2015 00:25 "gregorywringle" notifications@github.com пише:

I keep getting the following error on both sessions when I try to run them
in parallel.

info: [debug] Responding to client with error:
{"status":33,"value":{"message":"A new session could not be created.
(Original error: Instruments crashed on startup)","origValue":"Instruments
crashed on startup"},"sessionId":null}

Is there something special I need?
I have Appium 1.4.13 and Xcode 7.0 beta 5

/Applications/Appium-1.4.13.app/Contents/Resources/node lib/server/main.js
--command-timeout 7200 -p 4723 -bp 6002 --tmp ~/temp/temp2/
--native-instruments-lib

/Applications/Appium-1.4.13.app/Contents/Resources/node/bin/node
lib/server/main.js --command-timeout 7200 -p 4726 -bp 6001 --tmp
~/temp/temp1/ --native-instruments-lib


Reply to this email directly or view it on GitHub
#3637 (comment).

shady333 commented Nov 25, 2015

we are on appium 1.3.7 and xcode 7
25 лист. 2015 00:25 "gregorywringle" notifications@github.com пише:

I keep getting the following error on both sessions when I try to run them
in parallel.

info: [debug] Responding to client with error:
{"status":33,"value":{"message":"A new session could not be created.
(Original error: Instruments crashed on startup)","origValue":"Instruments
crashed on startup"},"sessionId":null}

Is there something special I need?
I have Appium 1.4.13 and Xcode 7.0 beta 5

/Applications/Appium-1.4.13.app/Contents/Resources/node lib/server/main.js
--command-timeout 7200 -p 4723 -bp 6002 --tmp ~/temp/temp2/
--native-instruments-lib

/Applications/Appium-1.4.13.app/Contents/Resources/node/bin/node
lib/server/main.js --command-timeout 7200 -p 4726 -bp 6001 --tmp
~/temp/temp1/ --native-instruments-lib


Reply to this email directly or view it on GitHub
#3637 (comment).

@marloncruz

This comment has been minimized.

Show comment
Hide comment
@marloncruz

marloncruz Nov 25, 2015

I have raised #5855 also a few days back.
Currently, my workaround is to run the appium under different logins (where appium is installed locally for each users)
If only one user creates all the appium nodes, all tests runs in parallel. But once one node issues driver.quit, all other instruments instance are killed.

marloncruz commented Nov 25, 2015

I have raised #5855 also a few days back.
Currently, my workaround is to run the appium under different logins (where appium is installed locally for each users)
If only one user creates all the appium nodes, all tests runs in parallel. But once one node issues driver.quit, all other instruments instance are killed.

@gregorywringle

This comment has been minimized.

Show comment
Hide comment
@gregorywringle

gregorywringle Nov 25, 2015

@marloncruz I setup 2 separate accounts each with a Appium locally installed and I get the following error:

WebKit Threading Violation - initial use of WebKit from a secondary thread.
Connection peer refused channel request for "com.apple.instruments.server.services.wireless"; channel canceled
...
info: [debug] Responding to client with error: {"status":33,"value":{"message":"A new session could not be created. (Original error: Instruments crashed on startup)","origValue":"Instruments crashed on startup"},"sessionId":null}

I can run each individually. Any ideas?

gregorywringle commented Nov 25, 2015

@marloncruz I setup 2 separate accounts each with a Appium locally installed and I get the following error:

WebKit Threading Violation - initial use of WebKit from a secondary thread.
Connection peer refused channel request for "com.apple.instruments.server.services.wireless"; channel canceled
...
info: [debug] Responding to client with error: {"status":33,"value":{"message":"A new session could not be created. (Original error: Instruments crashed on startup)","origValue":"Instruments crashed on startup"},"sessionId":null}

I can run each individually. Any ideas?

@shady333

This comment has been minimized.

Show comment
Hide comment
@shady333

shady333 Nov 25, 2015

does you have 2 different appium.app?
I'm running 2 instances from the same accout.
25 лист. 2015 21:55 "gregorywringle" notifications@github.com пише:

@marloncruz https://github.com/marloncruz I setup 2 separate accounts
each with a Appium locally installed and I get the following error:

WebKit Threading Violation - initial use of WebKit from a secondary thread.
Connection peer refused channel request for
"com.apple.instruments.server.services.wireless"; channel canceled
...
info: [debug] Responding to client with error:
{"status":33,"value":{"message":"A new session could not be created.
(Original error: Instruments crashed on startup)","origValue":"Instruments
crashed on startup"},"sessionId":null}

I can run each individually. Any ideas?


Reply to this email directly or view it on GitHub
#3637 (comment).

shady333 commented Nov 25, 2015

does you have 2 different appium.app?
I'm running 2 instances from the same accout.
25 лист. 2015 21:55 "gregorywringle" notifications@github.com пише:

@marloncruz https://github.com/marloncruz I setup 2 separate accounts
each with a Appium locally installed and I get the following error:

WebKit Threading Violation - initial use of WebKit from a secondary thread.
Connection peer refused channel request for
"com.apple.instruments.server.services.wireless"; channel canceled
...
info: [debug] Responding to client with error:
{"status":33,"value":{"message":"A new session could not be created.
(Original error: Instruments crashed on startup)","origValue":"Instruments
crashed on startup"},"sessionId":null}

I can run each individually. Any ideas?


Reply to this email directly or view it on GitHub
#3637 (comment).

@gregorywringle

This comment has been minimized.

Show comment
Hide comment
@gregorywringle

gregorywringle Nov 30, 2015

Yes I tried with 2 different appium.apps both from the same account and with 2 accounts each with its own appium.app. Neither worked. They have trouble with instruments that leads to a session failing to be created. If they're run in serial, both work.

To me it looks like instruments will not allow for parallel execution.
Device 0 : /Applications/Appium-1.4.8.app/Contces/node/bin/node lib/server/main.js --command-timeout 7200 --tmp ~/Temp/Old/ -bp 6001 --native-instruments-lib

info: [debug] [INST STDERR] instruments[9507:127086] Connection peer refused channel request for "com.apple.instruments.server.services.wireless"; channel canceled <DTXChannel: 0x7f80da1e39a0>
info: [debug] [INST STDERR] instruments[9507:126993] WebKit Threading Violation - initial use of WebKit from a secondary thread.
info: [debug] [INST STDERR] Instruments Usage Error : Specified target process is invalid: com.test.test
info: [debug] [INST STDERR] instruments, version 7.0 (58143.1)
usage: instruments [-t template] [-D document] [-l timeLimit] [-i #] [-w device] [[-p pid] | [application [-e variable value] [argument ...]]]
instruments[9507:126993] Connection peer refused channel request for "com.apple.instruments.server.services.wireless"; channel canceled <DTXChannel: 0x7f80d8ecbfd0>

Device 1 : /Applications/Appium-1.4.13.app/Contents/Resources/node/bin/node lib/serve-command-timeout 7200 -p 4726 --tmp ~/Temp/Temp -bp 6002 --native-instruments-lib

info: [debug] [INST STDERR] instruments[9483:126734] WebKit Threading Violation - initial use of WebKit from a secondary thread.
info: [debug] [INST STDERR] instruments[9483:126773] Connection peer refused channel request for "com.apple.instruments.server.services.mobilenotifications"; channel canceled <DTXChannel: 0x7fed3ce53f20>
info: [debug] [INST STDERR] instruments[9483:126773] Connection peer refused channel request for "com.apple.instruments.server.services.device.xpccontrol"; channel canceled <DTXChannel: 0x7fed3ce52d50>
Instruments Usage Error : Specified target process is invalid: com.test.test
instruments, version 7.0 (58143.1)
usage: instruments [-t template] [-D document] [-l timeLimit] [-i #] [-w device] [[-p pid] | [application [-e variable value] [argument ...]]]
info: [debug] [INST STDERR] instruments[9483:126773] Connection peer refused channel request for "com.apple.dt.Xcode.WatchProcessControl"; channel canceled <DTXChannel: 0x7fed3ce55e20>
info: [debug] [INST STDERR] instruments[9483:126773] Connection peer refused channel request for "com.apple.instruments.server.services.deviceinfo"; channel canceled <DTXChannel: 0x7fed3ce535f0>
info: [debug] [INST STDERR] instruments[9483:126773] Connection peer refused channel request for "com.apple.instruments.server.services.processcontrol"; channel canceled <DTXChannel: 0x7fed3ce53280>
info: [debug] [INST STDERR] instruments[9483:126773] Connection peer refused channel request for "com.apple.instruments.server.services.capabilities"; channel canceled <DTXChannel: 0x7fed3ce52150>
instruments[9483:126773] Connection peer refused channel request for "com.apple.instruments.server.services.device.applictionListing"; channel canceled <DTXChannel: 0x7fed3ce55300>
info: [debug] [INST STDERR] instruments[9483:126773] Connection peer refused channel request for "com.apple.instruments.server.services.processcontrol.posixspawn"; channel canceled <DTXChannel: 0x7fed3ce54260>
info: [debug] [INST STDERR] instruments[9483:126773] Connection peer refused channel request for "com.apple.instruments.server.services.wireless"; channel canceled <DTXChannel: 0x7fed3ce55cf0>

What could be the difference between our setup be?

gregorywringle commented Nov 30, 2015

Yes I tried with 2 different appium.apps both from the same account and with 2 accounts each with its own appium.app. Neither worked. They have trouble with instruments that leads to a session failing to be created. If they're run in serial, both work.

To me it looks like instruments will not allow for parallel execution.
Device 0 : /Applications/Appium-1.4.8.app/Contces/node/bin/node lib/server/main.js --command-timeout 7200 --tmp ~/Temp/Old/ -bp 6001 --native-instruments-lib

info: [debug] [INST STDERR] instruments[9507:127086] Connection peer refused channel request for "com.apple.instruments.server.services.wireless"; channel canceled <DTXChannel: 0x7f80da1e39a0>
info: [debug] [INST STDERR] instruments[9507:126993] WebKit Threading Violation - initial use of WebKit from a secondary thread.
info: [debug] [INST STDERR] Instruments Usage Error : Specified target process is invalid: com.test.test
info: [debug] [INST STDERR] instruments, version 7.0 (58143.1)
usage: instruments [-t template] [-D document] [-l timeLimit] [-i #] [-w device] [[-p pid] | [application [-e variable value] [argument ...]]]
instruments[9507:126993] Connection peer refused channel request for "com.apple.instruments.server.services.wireless"; channel canceled <DTXChannel: 0x7f80d8ecbfd0>

Device 1 : /Applications/Appium-1.4.13.app/Contents/Resources/node/bin/node lib/serve-command-timeout 7200 -p 4726 --tmp ~/Temp/Temp -bp 6002 --native-instruments-lib

info: [debug] [INST STDERR] instruments[9483:126734] WebKit Threading Violation - initial use of WebKit from a secondary thread.
info: [debug] [INST STDERR] instruments[9483:126773] Connection peer refused channel request for "com.apple.instruments.server.services.mobilenotifications"; channel canceled <DTXChannel: 0x7fed3ce53f20>
info: [debug] [INST STDERR] instruments[9483:126773] Connection peer refused channel request for "com.apple.instruments.server.services.device.xpccontrol"; channel canceled <DTXChannel: 0x7fed3ce52d50>
Instruments Usage Error : Specified target process is invalid: com.test.test
instruments, version 7.0 (58143.1)
usage: instruments [-t template] [-D document] [-l timeLimit] [-i #] [-w device] [[-p pid] | [application [-e variable value] [argument ...]]]
info: [debug] [INST STDERR] instruments[9483:126773] Connection peer refused channel request for "com.apple.dt.Xcode.WatchProcessControl"; channel canceled <DTXChannel: 0x7fed3ce55e20>
info: [debug] [INST STDERR] instruments[9483:126773] Connection peer refused channel request for "com.apple.instruments.server.services.deviceinfo"; channel canceled <DTXChannel: 0x7fed3ce535f0>
info: [debug] [INST STDERR] instruments[9483:126773] Connection peer refused channel request for "com.apple.instruments.server.services.processcontrol"; channel canceled <DTXChannel: 0x7fed3ce53280>
info: [debug] [INST STDERR] instruments[9483:126773] Connection peer refused channel request for "com.apple.instruments.server.services.capabilities"; channel canceled <DTXChannel: 0x7fed3ce52150>
instruments[9483:126773] Connection peer refused channel request for "com.apple.instruments.server.services.device.applictionListing"; channel canceled <DTXChannel: 0x7fed3ce55300>
info: [debug] [INST STDERR] instruments[9483:126773] Connection peer refused channel request for "com.apple.instruments.server.services.processcontrol.posixspawn"; channel canceled <DTXChannel: 0x7fed3ce54260>
info: [debug] [INST STDERR] instruments[9483:126773] Connection peer refused channel request for "com.apple.instruments.server.services.wireless"; channel canceled <DTXChannel: 0x7fed3ce55cf0>

What could be the difference between our setup be?

@shady333

This comment has been minimized.

Show comment
Hide comment
@shady333

shady333 Nov 30, 2015

we are using appium version 1.3.7
30 лист. 2015 19:37 "gregorywringle" notifications@github.com пише:

Yes I tried with 2 different appium.apps both from the same account and
with 2 accounts each with its own appium.app. Neither worked. They have
trouble with instruments that leads to a session failing to be created. If
they're run in serial, both work.

To me it looks like instruments will not allow for parallel execution.
Device 0 : /Applications/Appium-1.4.8.app/Contces/node/bin/node
lib/server/main.js --command-timeout 7200 --tmp ~/Temp/Old/ -bp 6001
--native-instruments-lib

info: [debug] [INST STDERR] instruments[9507:127086] Connection peer
refused channel request for
"com.apple.instruments.server.services.wireless"; channel canceled
info: [debug] [INST STDERR] instruments[9507:126993] WebKit Threading
Violation - initial use of WebKit from a secondary thread.
info: [debug] [INST STDERR] Instruments Usage Error : Specified target
process is invalid: com.test.test
info: [debug] [INST STDERR] instruments, version 7.0 (58143.1)
usage: instruments [-t template] [-D document] [-l timeLimit] [-i #] [-w
device] [[-p pid] | [application [-e variable value] [argument ...]]]
instruments[9507:126993] Connection peer refused channel request for
"com.apple.instruments.server.services.wireless"; channel canceled

Device 1 :
/Applications/Appium-1.4.13.app/Contents/Resources/node/bin/node
lib/serve-command-timeout 7200 -p 4726 --tmp ~/Temp/Temp -bp 6002
--native-instruments-lib

info: [debug] [INST STDERR] instruments[9483:126734] WebKit Threading
Violation - initial use of WebKit from a secondary thread.
info: [debug] [INST STDERR] instruments[9483:126773] Connection peer
refused channel request for
"com.apple.instruments.server.services.mobilenotifications"; channel
canceled
info: [debug] [INST STDERR] instruments[9483:126773] Connection peer
refused channel request for
"com.apple.instruments.server.services.device.xpccontrol"; channel canceled
Instruments Usage Error : Specified target process is invalid:
com.test.test
instruments, version 7.0 (58143.1)
usage: instruments [-t template] [-D document] [-l timeLimit] [-i #] [-w
device] [[-p pid] | [application [-e variable value] [argument ...]]]
info: [debug] [INST STDERR] instruments[9483:126773] Connection peer
refused channel request for "com.apple.dt.Xcode.WatchProcessControl";
channel canceled
info: [debug] [INST STDERR] instruments[9483:126773] Connection peer
refused channel request for
"com.apple.instruments.server.services.deviceinfo"; channel canceled
info: [debug] [INST STDERR] instruments[9483:126773] Connection peer
refused channel request for
"com.apple.instruments.server.services.processcontrol"; channel canceled
info: [debug] [INST STDERR] instruments[9483:126773] Connection peer
refused channel request for
"com.apple.instruments.server.services.capabilities"; channel canceled
instruments[9483:126773] Connection peer refused channel request for
"com.apple.instruments.server.services.device.applictionListing"; channel
canceled
info: [debug] [INST STDERR] instruments[9483:126773] Connection peer
refused channel request for
"com.apple.instruments.server.services.processcontrol.posixspawn"; channel
canceled
info: [debug] [INST STDERR] instruments[9483:126773] Connection peer
refused channel request for
"com.apple.instruments.server.services.wireless"; channel canceled

What could be the difference between our setup be?


Reply to this email directly or view it on GitHub
#3637 (comment).

shady333 commented Nov 30, 2015

we are using appium version 1.3.7
30 лист. 2015 19:37 "gregorywringle" notifications@github.com пише:

Yes I tried with 2 different appium.apps both from the same account and
with 2 accounts each with its own appium.app. Neither worked. They have
trouble with instruments that leads to a session failing to be created. If
they're run in serial, both work.

To me it looks like instruments will not allow for parallel execution.
Device 0 : /Applications/Appium-1.4.8.app/Contces/node/bin/node
lib/server/main.js --command-timeout 7200 --tmp ~/Temp/Old/ -bp 6001
--native-instruments-lib

info: [debug] [INST STDERR] instruments[9507:127086] Connection peer
refused channel request for
"com.apple.instruments.server.services.wireless"; channel canceled
info: [debug] [INST STDERR] instruments[9507:126993] WebKit Threading
Violation - initial use of WebKit from a secondary thread.
info: [debug] [INST STDERR] Instruments Usage Error : Specified target
process is invalid: com.test.test
info: [debug] [INST STDERR] instruments, version 7.0 (58143.1)
usage: instruments [-t template] [-D document] [-l timeLimit] [-i #] [-w
device] [[-p pid] | [application [-e variable value] [argument ...]]]
instruments[9507:126993] Connection peer refused channel request for
"com.apple.instruments.server.services.wireless"; channel canceled

Device 1 :
/Applications/Appium-1.4.13.app/Contents/Resources/node/bin/node
lib/serve-command-timeout 7200 -p 4726 --tmp ~/Temp/Temp -bp 6002
--native-instruments-lib

info: [debug] [INST STDERR] instruments[9483:126734] WebKit Threading
Violation - initial use of WebKit from a secondary thread.
info: [debug] [INST STDERR] instruments[9483:126773] Connection peer
refused channel request for
"com.apple.instruments.server.services.mobilenotifications"; channel
canceled
info: [debug] [INST STDERR] instruments[9483:126773] Connection peer
refused channel request for
"com.apple.instruments.server.services.device.xpccontrol"; channel canceled
Instruments Usage Error : Specified target process is invalid:
com.test.test
instruments, version 7.0 (58143.1)
usage: instruments [-t template] [-D document] [-l timeLimit] [-i #] [-w
device] [[-p pid] | [application [-e variable value] [argument ...]]]
info: [debug] [INST STDERR] instruments[9483:126773] Connection peer
refused channel request for "com.apple.dt.Xcode.WatchProcessControl";
channel canceled
info: [debug] [INST STDERR] instruments[9483:126773] Connection peer
refused channel request for
"com.apple.instruments.server.services.deviceinfo"; channel canceled
info: [debug] [INST STDERR] instruments[9483:126773] Connection peer
refused channel request for
"com.apple.instruments.server.services.processcontrol"; channel canceled
info: [debug] [INST STDERR] instruments[9483:126773] Connection peer
refused channel request for
"com.apple.instruments.server.services.capabilities"; channel canceled
instruments[9483:126773] Connection peer refused channel request for
"com.apple.instruments.server.services.device.applictionListing"; channel
canceled
info: [debug] [INST STDERR] instruments[9483:126773] Connection peer
refused channel request for
"com.apple.instruments.server.services.processcontrol.posixspawn"; channel
canceled
info: [debug] [INST STDERR] instruments[9483:126773] Connection peer
refused channel request for
"com.apple.instruments.server.services.wireless"; channel canceled

What could be the difference between our setup be?


Reply to this email directly or view it on GitHub
#3637 (comment).

@gregorywringle

This comment has been minimized.

Show comment
Hide comment
@gregorywringle

gregorywringle Nov 30, 2015

Alright this is frustrating. I'm going to lay everything out and hopefully you can spot something.

On a single user running 2 Appium.app 1.3.7 using Selenium Grid 2.48.2.
Device 0 : /Applications/Appium-1.3.7.app/Contces/node/bin/node lib/server/main.js --command-timeout 7200 --tmp ~/Temp/Old/ -bp 6001 --native-instruments-lib --nodeconfig ~/Documents/selgridi4.json

Device 1 : /Applications/Appium-1.3.7-2.app/Contents/Resources/node/bin/node lib/servercommand-timeout 7200 -p 4726 --tmp ~/Temp/Temp/ -bp 6002 --native-instruments-lib --nodeconfig ~/Documents/selgridi6.json

Selenium hub : java -jar selenium-server-standalone-2.48.2.jar -role hub

selgridi4.json
{
"capabilities":
[
{
"browserName": "iPhone4S",
"version":"7.1.2",
"maxInstances": 1,
"platform":"MAC"
}
],
"configuration":
{
"cleanUpCycle":2000,
"timeout":30000,
"proxy": "org.openqa.grid.selenium.proxy.DefaultRemoteProxy",
"url":"http://127.0.0.1:4723/wd/hub",
"host": "127.0.0.1",
"port": 4723,
"maxSession": 1,
"register": true,
"registerCycle": 5000,
"hubPort": 4444,
"hubHost": "127.0.0.1"
}
}

selgridi6.json
{
"capabilities":
[
{
"browserName": "iPhone6",
"version":"8.1.2",
"maxInstances": 1,
"platform":"MAC"
}
],
"configuration":
{
"cleanUpCycle":2000,
"timeout":30000,
"proxy": "org.openqa.grid.selenium.proxy.DefaultRemoteProxy",
"url":"http://127.0.0.1:4726/wd/hub",
"host": "127.0.0.1",
"port": 4726,
"maxSession": 1,
"register": true,
"registerCycle": 5000,
"hubPort": 4444,
"hubHost": "127.0.0.1"
}
}

Both appium sessions are able to connect to the selenium hub.

Both fail with instruments crashing.

When I add --address 127.0.0.1 they both fail with instruments crashing.

gregorywringle commented Nov 30, 2015

Alright this is frustrating. I'm going to lay everything out and hopefully you can spot something.

On a single user running 2 Appium.app 1.3.7 using Selenium Grid 2.48.2.
Device 0 : /Applications/Appium-1.3.7.app/Contces/node/bin/node lib/server/main.js --command-timeout 7200 --tmp ~/Temp/Old/ -bp 6001 --native-instruments-lib --nodeconfig ~/Documents/selgridi4.json

Device 1 : /Applications/Appium-1.3.7-2.app/Contents/Resources/node/bin/node lib/servercommand-timeout 7200 -p 4726 --tmp ~/Temp/Temp/ -bp 6002 --native-instruments-lib --nodeconfig ~/Documents/selgridi6.json

Selenium hub : java -jar selenium-server-standalone-2.48.2.jar -role hub

selgridi4.json
{
"capabilities":
[
{
"browserName": "iPhone4S",
"version":"7.1.2",
"maxInstances": 1,
"platform":"MAC"
}
],
"configuration":
{
"cleanUpCycle":2000,
"timeout":30000,
"proxy": "org.openqa.grid.selenium.proxy.DefaultRemoteProxy",
"url":"http://127.0.0.1:4723/wd/hub",
"host": "127.0.0.1",
"port": 4723,
"maxSession": 1,
"register": true,
"registerCycle": 5000,
"hubPort": 4444,
"hubHost": "127.0.0.1"
}
}

selgridi6.json
{
"capabilities":
[
{
"browserName": "iPhone6",
"version":"8.1.2",
"maxInstances": 1,
"platform":"MAC"
}
],
"configuration":
{
"cleanUpCycle":2000,
"timeout":30000,
"proxy": "org.openqa.grid.selenium.proxy.DefaultRemoteProxy",
"url":"http://127.0.0.1:4726/wd/hub",
"host": "127.0.0.1",
"port": 4726,
"maxSession": 1,
"register": true,
"registerCycle": 5000,
"hubPort": 4444,
"hubHost": "127.0.0.1"
}
}

Both appium sessions are able to connect to the selenium hub.

Both fail with instruments crashing.

When I add --address 127.0.0.1 they both fail with instruments crashing.

@gregorywringle

This comment has been minimized.

Show comment
Hide comment
@gregorywringle

gregorywringle Nov 30, 2015

I went back to the bare basic: https://discuss.appium.io/t/selenium-grid-testng-appium-pseudo-code-parallel-multiple-devices/3336

And that failed with the instruments. Is there something special you did with your Xcode/instruments? I'm using Xcode v7.0 beta 5 with default instruments. I also have Xcode 6.4 installed. I use xcode-select to switch to 7.0.

gregorywringle commented Nov 30, 2015

I went back to the bare basic: https://discuss.appium.io/t/selenium-grid-testng-appium-pseudo-code-parallel-multiple-devices/3336

And that failed with the instruments. Is there something special you did with your Xcode/instruments? I'm using Xcode v7.0 beta 5 with default instruments. I also have Xcode 6.4 installed. I use xcode-select to switch to 7.0.

@gregorywringle

This comment has been minimized.

Show comment
Hide comment
@gregorywringle

gregorywringle Dec 3, 2015

@shady333 are you using vms on your mac?

gregorywringle commented Dec 3, 2015

@shady333 are you using vms on your mac?

@shady333

This comment has been minimized.

Show comment
Hide comment
@shady333

shady333 Dec 3, 2015

I'm using macmini
3 груд. 2015 19:44 "gregorywringle" notifications@github.com пише:

@shady333 https://github.com/shady333 are you using vms on your mac?


Reply to this email directly or view it on GitHub
#3637 (comment).

shady333 commented Dec 3, 2015

I'm using macmini
3 груд. 2015 19:44 "gregorywringle" notifications@github.com пише:

@shady333 https://github.com/shady333 are you using vms on your mac?


Reply to this email directly or view it on GitHub
#3637 (comment).

@cnrani

This comment has been minimized.

Show comment
Hide comment
@cnrani

cnrani Apr 4, 2016

@shady333 How are you using your Macmini to run automated tests on multiple mobile devices. I am going to explore on this. If you have already explored on this please share the documents and POC on this..
Much appreciate the help provided.
Thanks in advance

cnrani commented Apr 4, 2016

@shady333 How are you using your Macmini to run automated tests on multiple mobile devices. I am going to explore on this. If you have already explored on this please share the documents and POC on this..
Much appreciate the help provided.
Thanks in advance

@saikrishna321

This comment has been minimized.

Show comment
Hide comment
@qakapil

This comment has been minimized.

Show comment
Hide comment
@qakapil

qakapil May 16, 2016

Did anyone have any luck running iOS appium tests (real devices) in parallel ? I tried this both with and without selenium grid but no luck. The procedure which I followed is pretty much like gregorywringle mentioned above. My appium version is 1.4.16 and xcode version is 7.3.
When I try to run tests in parallel on two connected devices, test run fine on one of the devices but the other one hangs and fails with this error -

self.error_handler.check_response(response)
File "/Library/Python/2.7/site-packages/appium/webdriver/errorhandler.py", line 29, in check_response
raise wde
WebDriverException: Message: Instruments died while responding to command, please check appium logs

qakapil commented May 16, 2016

Did anyone have any luck running iOS appium tests (real devices) in parallel ? I tried this both with and without selenium grid but no luck. The procedure which I followed is pretty much like gregorywringle mentioned above. My appium version is 1.4.16 and xcode version is 7.3.
When I try to run tests in parallel on two connected devices, test run fine on one of the devices but the other one hangs and fails with this error -

self.error_handler.check_response(response)
File "/Library/Python/2.7/site-packages/appium/webdriver/errorhandler.py", line 29, in check_response
raise wde
WebDriverException: Message: Instruments died while responding to command, please check appium logs

@anish10110

This comment has been minimized.

Show comment
Hide comment
@anish10110

anish10110 Nov 17, 2016

http://automationtestinghub.com/appium-parallel-execution/

The above article uses Java Thread and Runnable interface for parallel execution on 2 android devices connected to a single machine.

The trick is that we need to provide different values for Appium port, Bootstrap Port, Device ID (ie UDID, not Device Name) , Chrome Driver port (if using Chrome Browser in the app).

anish10110 commented Nov 17, 2016

http://automationtestinghub.com/appium-parallel-execution/

The above article uses Java Thread and Runnable interface for parallel execution on 2 android devices connected to a single machine.

The trick is that we need to provide different values for Appium port, Bootstrap Port, Device ID (ie UDID, not Device Name) , Chrome Driver port (if using Chrome Browser in the app).

@monism

This comment has been minimized.

Show comment
Hide comment
@monism

monism Aug 18, 2017

is it possible to run appium (IOS) on two different user accounts of same machine using grid

monism commented Aug 18, 2017

is it possible to run appium (IOS) on two different user accounts of same machine using grid

@saikrishna321

This comment has been minimized.

Show comment
Hide comment
@saikrishna321
Member

saikrishna321 commented Aug 18, 2017

@monism

This comment has been minimized.

Show comment
Hide comment
@monism

monism Aug 18, 2017

@saikrishna321 Thanks but as mentioned in your git page , i am using Xcode 8.3 only , so if you please guide me what extra changes i need to do to make it up and running using grid or do i need Xcode beta-9 only to achieve this

monism commented Aug 18, 2017

@saikrishna321 Thanks but as mentioned in your git page , i am using Xcode 8.3 only , so if you please guide me what extra changes i need to do to make it up and running using grid or do i need Xcode beta-9 only to achieve this

@saikrishna321

This comment has been minimized.

Show comment
Hide comment
@saikrishna321

saikrishna321 Aug 18, 2017

Member

for parallel simulators you need to xcode9-beta. Please raise in discuss.appium.io for help.

Member

saikrishna321 commented Aug 18, 2017

for parallel simulators you need to xcode9-beta. Please raise in discuss.appium.io for help.

@monism

This comment has been minimized.

Show comment
Hide comment
@monism

monism Aug 23, 2017

@saikrishna321 i installed Xcode 9 but it seems appium 1.6.5 is not compatible so i downloaded Appioum 1.6.6-beta.4 , but still i am getting below message "[XCUITest] Error: Xcode version 9.0 is not yet supported", Can you please help in solving this issue

monism commented Aug 23, 2017

@saikrishna321 i installed Xcode 9 but it seems appium 1.6.5 is not compatible so i downloaded Appioum 1.6.6-beta.4 , but still i am getting below message "[XCUITest] Error: Xcode version 9.0 is not yet supported", Can you please help in solving this issue

@saikrishna321

This comment has been minimized.

Show comment
Hide comment
@saikrishna321

saikrishna321 Aug 23, 2017

Member

@monism you need to have the latest beta.4 uninstall and reinstall npm install -g appium@beta

i use beta.4 and works with xcode9-beta 6

Member

saikrishna321 commented Aug 23, 2017

@monism you need to have the latest beta.4 uninstall and reinstall npm install -g appium@beta

i use beta.4 and works with xcode9-beta 6

@monism

This comment has been minimized.

Show comment
Hide comment
@monism

monism Aug 24, 2017

Thanks , its working for me , but whatever xpath i was using so far, with Appium@beta none of the xpaths are getting identified now, i am also using Xcuitest = automationame, but still doesn't help

monism commented Aug 24, 2017

Thanks , its working for me , but whatever xpath i was using so far, with Appium@beta none of the xpaths are getting identified now, i am also using Xcuitest = automationame, but still doesn't help

@monism

This comment has been minimized.

Show comment
Hide comment
@monism

monism Aug 24, 2017

And if i try to open IPad Air 2 of 10.3 and IPad Air 2 of 9.3 , both simulators will be opened but app will get loaded to one only.

[Xcode] 2017-08-24 15:40:31.995 WebDriverAgentRunner-Runner[60195:242385] Built at Aug 24 2017 15:40:21
[Xcode] 2017-08-24 15:40:32.009 WebDriverAgentRunner-Runner[60195:242385] Failed to start web server on port 8100 with error Error Domain=com.facebook.WebDriverAgent Code=1 "Unable to start web server on port 8100" UserInfo={NSLocalizedDescription=Unable to start web server on port 8100, NSUnderlyingError=0x61000024f1b0 {Error Domain=NSPOSIXErrorDomain Code=48 "Address already in use" UserInfo={NSLocalizedDescription=Address already in use, NSLocalizedFailureReason=Error in bind() function}}}
[Xcode] 2017-08-24 15:40:32.009 WebDriverAgentRunner-Runner[60195:242385] Last attempt to start web server failed with error Error Domain=com.facebook.WebDriverAgent Code=1 "Unable to start web server on port 8100" UserInfo={NSLocalizedDescription=Unable to start web server on port 8100, NSUnderlyingError=0x61000024f1b0 {Error Domain=NSPOSIXErrorDomain Code=48 "Address already in use" UserInfo={NSLocalizedDescription=Address already in use, NSLocalizedFailureReason=Error in bind() function}}}
[Xcode] 2017-08-24 15:40:37.946 WebDriverAgentRunner-Runner[60208:242915] Running tests...
[Xcode] 2017-08-24 15:40:38.657 WebDriverAgentRunner-Runner[60208:242915] Continuing to run tests in the background with task ID 1
[Xcode]
[Xcode] Restarting after unexpected exit or crash in UITestingUITests/testRunner; summary will include totals from previous launches.
[Xcode]
[Xcode] Test Suite 'Selected tests' started at 2017-08-24 15:40:38.762
[Xcode] Test Suite 'WebDriverAgentLib.framework' started at 2017-08-24 15:40:38.763
[Xcode] Test Suite 'WebDriverAgentLib.framework' passed at 2017-08-24 15:40:38.763.
[Xcode] Executed 0 tests, with 0 failures (0 unexpected) in 0.000 (0.000) seconds
[Xcode] Test Suite 'WebDriverAgentRunner.xctest' started at 2017-08-24 15:40:38.764
[Xcode] Test Suite 'WebDriverAgentRunner.xctest' failed at 2017-08-24 15:40:38.764.
[Xcode] Executed 1 test, with 1 failure (0 unexpected) in 0.000 (0.000) seconds
[Xcode] Test Suite 'Selected tests' failed at 2017-08-24 15:40:38.764.
[Xcode] Executed 1 test, with 1 failure (0 unexpected) in 0.000 (0.002) seconds

monism commented Aug 24, 2017

And if i try to open IPad Air 2 of 10.3 and IPad Air 2 of 9.3 , both simulators will be opened but app will get loaded to one only.

[Xcode] 2017-08-24 15:40:31.995 WebDriverAgentRunner-Runner[60195:242385] Built at Aug 24 2017 15:40:21
[Xcode] 2017-08-24 15:40:32.009 WebDriverAgentRunner-Runner[60195:242385] Failed to start web server on port 8100 with error Error Domain=com.facebook.WebDriverAgent Code=1 "Unable to start web server on port 8100" UserInfo={NSLocalizedDescription=Unable to start web server on port 8100, NSUnderlyingError=0x61000024f1b0 {Error Domain=NSPOSIXErrorDomain Code=48 "Address already in use" UserInfo={NSLocalizedDescription=Address already in use, NSLocalizedFailureReason=Error in bind() function}}}
[Xcode] 2017-08-24 15:40:32.009 WebDriverAgentRunner-Runner[60195:242385] Last attempt to start web server failed with error Error Domain=com.facebook.WebDriverAgent Code=1 "Unable to start web server on port 8100" UserInfo={NSLocalizedDescription=Unable to start web server on port 8100, NSUnderlyingError=0x61000024f1b0 {Error Domain=NSPOSIXErrorDomain Code=48 "Address already in use" UserInfo={NSLocalizedDescription=Address already in use, NSLocalizedFailureReason=Error in bind() function}}}
[Xcode] 2017-08-24 15:40:37.946 WebDriverAgentRunner-Runner[60208:242915] Running tests...
[Xcode] 2017-08-24 15:40:38.657 WebDriverAgentRunner-Runner[60208:242915] Continuing to run tests in the background with task ID 1
[Xcode]
[Xcode] Restarting after unexpected exit or crash in UITestingUITests/testRunner; summary will include totals from previous launches.
[Xcode]
[Xcode] Test Suite 'Selected tests' started at 2017-08-24 15:40:38.762
[Xcode] Test Suite 'WebDriverAgentLib.framework' started at 2017-08-24 15:40:38.763
[Xcode] Test Suite 'WebDriverAgentLib.framework' passed at 2017-08-24 15:40:38.763.
[Xcode] Executed 0 tests, with 0 failures (0 unexpected) in 0.000 (0.000) seconds
[Xcode] Test Suite 'WebDriverAgentRunner.xctest' started at 2017-08-24 15:40:38.764
[Xcode] Test Suite 'WebDriverAgentRunner.xctest' failed at 2017-08-24 15:40:38.764.
[Xcode] Executed 1 test, with 1 failure (0 unexpected) in 0.000 (0.000) seconds
[Xcode] Test Suite 'Selected tests' failed at 2017-08-24 15:40:38.764.
[Xcode] Executed 1 test, with 1 failure (0 unexpected) in 0.000 (0.002) seconds

@saikrishna321

This comment has been minimized.

Show comment
Hide comment
@saikrishna321

saikrishna321 Aug 24, 2017

Member

@monism you need to specify different wdaPort

Member

saikrishna321 commented Aug 24, 2017

@monism you need to specify different wdaPort

@monismajeed

This comment has been minimized.

Show comment
Hide comment
@monismajeed

monismajeed Aug 28, 2017

@saikrishna321
Ya that works thanks , I have small doubt , i am going to use grid for running IOS Appium cases , and if i have 2 machines as a node and i have set up two accounts on both machines, can i use as both accounts of both machines as nodes and setup in grid.

monismajeed commented Aug 28, 2017

@saikrishna321
Ya that works thanks , I have small doubt , i am going to use grid for running IOS Appium cases , and if i have 2 machines as a node and i have set up two accounts on both machines, can i use as both accounts of both machines as nodes and setup in grid.

@monismajeed

This comment has been minimized.

Show comment
Hide comment
@monismajeed

monismajeed Sep 5, 2017

@saikrishna321

I have a mac which is having 2 accounts account1 and account2, I have setted up grid where account1 is acting as a hub and node as well and account2 is acting another node , both are having appium running with different ports, but when i run cases in parallel, only in one account simulator opens and in another it gives below error
org.openqa.selenium.WebDriverException: An unknown server-side error occurred while processing the command. Original error: Command 'osascript -e 'tell application "System Events" to count processes whose bundle identifier is "com.apple.iphonesimulator"'' exited with code 1 (WARNING: The server did not provide any stacktrace information)

Xcode: Xcode-9-beta
Appium: appium@beta

Any help will be appreciated

monismajeed commented Sep 5, 2017

@saikrishna321

I have a mac which is having 2 accounts account1 and account2, I have setted up grid where account1 is acting as a hub and node as well and account2 is acting another node , both are having appium running with different ports, but when i run cases in parallel, only in one account simulator opens and in another it gives below error
org.openqa.selenium.WebDriverException: An unknown server-side error occurred while processing the command. Original error: Command 'osascript -e 'tell application "System Events" to count processes whose bundle identifier is "com.apple.iphonesimulator"'' exited with code 1 (WARNING: The server did not provide any stacktrace information)

Xcode: Xcode-9-beta
Appium: appium@beta

Any help will be appreciated

@mykola-mokhnach

This comment has been minimized.

Show comment
Hide comment
@mykola-mokhnach

mykola-mokhnach Sep 5, 2017

Collaborator

@monismajeed have you tried to execute the above command manually from the Terminal? What output do you get there?

Collaborator

mykola-mokhnach commented Sep 5, 2017

@monismajeed have you tried to execute the above command manually from the Terminal? What output do you get there?

@saikrishna321

This comment has been minimized.

Show comment
Hide comment
@saikrishna321

saikrishna321 Sep 6, 2017

Member

@monismajeed +1 to @mykola-mokhnach comment.. try that n check ..

Question: Why are you having two accounts to run parallel, when its possible in single mac Host

Member

saikrishna321 commented Sep 6, 2017

@monismajeed +1 to @mykola-mokhnach comment.. try that n check ..

Question: Why are you having two accounts to run parallel, when its possible in single mac Host

@monismajeed

This comment has been minimized.

Show comment
Hide comment
@monismajeed

monismajeed Sep 11, 2017

@saikrishna321 It is not coming only if i run them in separate accounts even if use same account sometime i am getting this intermittent issue

@mykola-mokhnach If i run above command , it says " osascript -e tell: command not found"

monismajeed commented Sep 11, 2017

@saikrishna321 It is not coming only if i run them in separate accounts even if use same account sometime i am getting this intermittent issue

@mykola-mokhnach If i run above command , it says " osascript -e tell: command not found"

@mykola-mokhnach

This comment has been minimized.

Show comment
Hide comment
@mykola-mokhnach

mykola-mokhnach Sep 11, 2017

Collaborator

If i run above command , it says " osascript -e tell: command not found"

Then your machine is either damaged and you have to try another one or PATH environment variable is not set properly for the main Appium process. The utility above should be always available by /usr/bin/osascript path

Collaborator

mykola-mokhnach commented Sep 11, 2017

If i run above command , it says " osascript -e tell: command not found"

Then your machine is either damaged and you have to try another one or PATH environment variable is not set properly for the main Appium process. The utility above should be always available by /usr/bin/osascript path

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment