-
-
Notifications
You must be signed in to change notification settings - Fork 101
src: update constants to match V8 6.4 #186
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
Conversation
|
@bnoordhuis are you getting |
594644f to
3a6cd49
Compare
|
@bnoordhuis I ran Running test suite here didn't present any error. |
|
@Drieger The test suites here only test up to v9.x (v8 v6.2) |
|
@joyeecheung I ran tests against Node.js master, using the following command: TEST_LLDB_BINARY=`which lldb-5.0` LLNODE_NODE_EXE=/Workspace/node/node npm run testIs that right? How could I run test suite against the correct V8 version? |
|
@Drieger You can alter your |
|
@Drieger if you want to use nvm: https://gist.github.com/chicoxyzzy/77dcbf21485d80b3ad870ed0d3286579 |
@mmarchini That, and a few others. With lldb-902.0.79.2: Details |
findjsobjects -d test relies on how the hidden-class it tests is built. Zlib is a builtin from Node.js, therefore we cannot be sure about the order attributes are assigned to the class, making its hidden-class unpredictable. Using a class from our fixtures (in this case, Class) makes the test more predictable across Node.js versions and across multiple Operating Systems. Ref: nodejs#186
findjsobjects -d test relies on how the hidden-class it tests is built. Zlib is a builtin from Node.js, therefore we cannot be sure about the order attributes are assigned to the class, making its hidden-class unpredictable. Using a class from our fixtures (in this case, Class) makes the test more predictable across Node.js versions and across multiple Operating Systems. Ref: #186
Fixes: #158