Skip to content
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

error in clearDeviceRegistryLockFile() when running detox test #771

Closed
dat00ste opened this issue Jun 5, 2018 · 6 comments
Closed

error in clearDeviceRegistryLockFile() when running detox test #771

dat00ste opened this issue Jun 5, 2018 · 6 comments

Comments

@dat00ste
Copy link

dat00ste commented Jun 5, 2018

For usage help, ask a question on Stack Overflow with the detox tag. The issues section of the project is meant for opening bug reports and enhancement requests of Detox. We use it to automatically track the change log

IMPORTANT: Use search before opening an issue. Duplicate issues will simply be closed.

Description

Since detox 7.4.0 I cannot start detox test. It fails on clearDeviceRegistryLockFile that was added in #609.
I'm using windows.

$ detox test -c android.emu.release --loglevel verbose
fs.js:646
return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
^

Error: ENOENT: no such file or directory, open 'C:\Users\stina\AppData\Local\data\Detox\device.registry.state.lock'
at Object.fs.openSync (fs.js:646:18)
at Object.fs.writeFileSync (fs.js:1299:33)
at clearDeviceRegistryLockFile (C:\Users\stina\code\App\powerup\node_modules\detox\local-cli\detox-test.js:171:6)

detox 7.3.7 works fine (with some minor manual changes )

Detox, Node, Device, Xcode and macOS Versions

  • Detox: 7.4.0
  • React Native: 0.55.3
  • Node: 8.11.1
  • Device: -
  • Xcode: -
  • macOS: -
@noomorph
Copy link
Collaborator

noomorph commented Jun 5, 2018

If nobody takes this issue, I can try to reproduce after June 10th, after I return from vacation. Or maybe @simonbuchan might want to take a look?

@simonbuchan
Copy link
Contributor

Hmm, I migrated up to 7.4.0 without trouble. Looks like it just hasn't created the data directory, so if that got broken, shouldn't be too hard to track down (and maybe isn't even windows?)

@noomorph
Copy link
Collaborator

noomorph commented Jun 6, 2018

Hmm, I migrated up to 7.4.0 without trouble.

That was the essence of my inquiry. Thanks much, Simon!

@dat00ste
Copy link
Author

dat00ste commented Jun 7, 2018

Thanks for the replies!
Yes, the data directory is missing, when should it be created?

@rotemmiz
Copy link
Member

rotemmiz commented Jun 7, 2018

This is an actual issue. We need to ensure the directory will be created if doesn't exist

@rotemmiz
Copy link
Member

Fixed in #781

@wix wix locked and limited conversation to collaborators Jul 23, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants