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

nodejs 9.2 failure #5030

Closed
cwmoo740 opened this issue Dec 6, 2017 · 3 comments · Fixed by #5031
Closed

nodejs 9.2 failure #5030

cwmoo740 opened this issue Dec 6, 2017 · 3 comments · Fixed by #5031

Comments

@cwmoo740
Copy link

cwmoo740 commented Dec 6, 2017

Do you want to request a feature or report a bug?

Bug

What is the current behavior?

linux 4.14, [email protected], node v9.2.0

jest

RUNS  src/dates/__tests__/math.test.ts
/usr/bin/node[23297]: ../src/node_file.cc:835:void node::RealPath(const v8::FunctionCallbackInfo<v8::Value>&): Assertion `(args.Length()) >= (2)' failed.
 1: node::Abort() [node]
 2: node::Assert(char const* const (*) [4]) [node]
 3: 0x5595756fed3d [node]
 4: v8::internal::FunctionCallbackArguments::Call(void (*)(v8::FunctionCallbackInfo<v8::Value> const&)) [node]
 5: 0x5595750292df [node]
 6: 0x55957502982f [node]
 7: 0x2e88c60842fd
error Command failed with signal "SIGABRT".

linux 4.14, [email protected], node v8.9.2 - works as expected.

This seems to be true for any example - I created a simple-as-possible example to make sure it was still broken.

https://github.com/cwmoo740/jest-node-9

@SimenB
Copy link
Member

SimenB commented Dec 6, 2017

Can reproduce on Jest's own test suite... Will look through node's changelog to see if anything sticks out

@SimenB
Copy link
Member

SimenB commented Dec 6, 2017

git bisect blames nodejs/node#15776

SimenB added a commit to SimenB/jest that referenced this issue Dec 6, 2017
cpojer pushed a commit that referenced this issue Dec 7, 2017
* Pass in encoding to `realpath` call

Fixes #5030

* Use `fs.realpathSync.native` if it exists

* update changelog
@github-actions
Copy link

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.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 13, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants