-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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 when nodegit is referenced from several places #3550
Comments
Looks like we hit similar problem as here: #2029 |
Closing due to: #3552 |
jmurzy
added a commit
to jmurzy/nodegit
that referenced
this issue
Aug 14, 2017
A summary of why this change was required is discussed in the following issues: jestjs/jest#3552 jestjs/jest#3550 nodejs/node#5016
jmurzy
added a commit
to jmurzy/nodegit
that referenced
this issue
Aug 14, 2017
Discussion on why this change was required can be found in the following issues: jestjs/jest#3552 jestjs/jest#3550 nodejs/node#5016
jmurzy
added a commit
to jmurzy/nodegit
that referenced
this issue
Aug 14, 2017
Discussion on why this change was required can be found in the following issues: jestjs/jest#3552 jestjs/jest#3550 nodejs/node#5016
sorenlouv
pushed a commit
to sorenlouv/nodegit
that referenced
this issue
Oct 1, 2017
Discussion on why this change was required can be found in the following issues: jestjs/jest#3552 jestjs/jest#3550 nodejs/node#5016
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If nodegit is referenced in more than 1 test file (even not directly) then Jest throws random errors related to promisify-node like:
TypeError: Cannot convert undefined or null to object at processExports (node_modules/promisify-node/index.js:44:16) at Object.<anonymous> (index.js:1:106) at Object.<anonymous> (__tests__/index.test.js:1:100)
Steps could be following:
I've created a repo illustrating that.
https://github.com/stukalin/jest-nodegit-issue
Simply run yarn install && yarn test. Note, that sometimes tests pass, but simply repeat 2-3 times.
With --no-cache it works
My conf:
OS: Ubuntu 16.04
Jest: v20.0.1
nodegit: latest (0.18.3)
yarn: 0.23.4
npm: 3.10.10
node: v6.10.2
The text was updated successfully, but these errors were encountered: