Skip to content
New issue

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

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

Already on GitHub? # to your account

Command failed: /usr/bin/xcrun simctl shutdown #671

Closed
xcarpentier opened this issue Apr 13, 2018 · 5 comments
Closed

Command failed: /usr/bin/xcrun simctl shutdown #671

xcarpentier opened this issue Apr 13, 2018 · 5 comments

Comments

@xcarpentier
Copy link
Contributor

I'm using detox on circleci execute into a macos box.

  • Detox version: 7.3.3

Stacktrace

detox info 14: Shutting down 7171AA16-2E5C-4DEB-B845-7B6DB382CC58... 
  1) "after all" hook

  27 passing (3m)
  1 failing

  1)  "after all" hook:
     ChildProcessError: Command failed: /usr/bin/xcrun simctl shutdown 7171AA16-2E5C-4DEB-B845-7B6DB382CC58
2018-04-12 08:42:16.388 simctl[6192:33658] CoreSimulatorService connection interrupted.  Resubscribing to notifications.
2018-04-12 08:42:16.388 simctl[6192:33660] CoreSimulatorService connection interrupted.  Resubscribing to notifications.
An error was encountered processing the command (domain=NSPOSIXErrorDomain, code=53):
Error returned in reply: Connection interrupted
Software caused connection abort
 `/usr/bin/xcrun simctl shutdown 7171AA16-2E5C-4DEB-B845-7B6DB382CC58` (exited with error code 53)
      at callback (node_modules/child-process-promise/lib/index.js:33:27)
      at ChildProcess.exithandler (child_process.js:282:5)
      at maybeClose (internal/child_process.js:925:16)
      at Socket.stream.socket.on (internal/child_process.js:346:11)
      at Pipe._handle.close [as _onclose] (net.js:554:12)
@rotemmiz
Copy link
Member

Does this also happen locally ?
I have a hunch it's a circleci thing.
Try starting up a simulator, then shutting it down, regardless of Detox, see if circleCI likes it...

/usr/bin/xcrun simctl launch 7171AA16-2E5C-4DEB-B845-7B6DB382CC58
/usr/bin/xcrun simctl shutdown 7171AA16-2E5C-4DEB-B845-7B6DB382CC58

@xcarpentier
Copy link
Contributor Author

xcarpentier commented Apr 18, 2018

@rotemmiz actually this is intermittent.
I will test on attaching a bash session and let you know ...

I take some screenshot too, by using this:

const saveScreenshot = fileName =>
  exec(
    `xcrun simctl io booted screenshot \${CIRCLE_ARTIFACTS:='./e2e/screenshots'}/${fileName}.png`
  )

Do you think that may cause side effects ?

@rotemmiz
Copy link
Member

I don't believe it will.
I think this is an issue with circleci VMs.
If your bash script indeed reproduces this error try also opening a ticket with them.

@xcarpentier
Copy link
Contributor Author

@LeoNatan
Copy link
Contributor

LeoNatan commented May 3, 2018

Either way, not a Detox issue.

@LeoNatan LeoNatan closed this as completed May 3, 2018
@wix wix locked and limited conversation to collaborators Jul 23, 2018
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants