-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
207 failures in v8 tests within node tree #7477
Comments
I suspect this is because of the ABI compatibility changes. cc @ofrobots I'd like to test without the two related commits but I get the following error with
|
to confirm did you :
|
yes, I have depot_tools in my path |
@targos is the depo tools in your path an absolute path? I had some weirdness with relative |
it is absolute. I am currently on OSX and have the exact same error than on Linux. |
It seems like the A normal build of Node doesn't build V8 at the above location. |
Yeah I just realized that I have to run |
The test targets expect that V8 is built in deps/v8/out Ref: nodejs#7477
I don't see these failures w/ |
Err.. actually ignore my last statement about testing with |
I can reproduce the failures on master. Trying now without the 2 commits. |
I think |
Restore whitespaces in *.golden files. They were lost when I landed the V8 5.1 update. Fixes: nodejs#7477
Kicking off CI run to validate issue is resolved: https://ci.nodejs.org/job/node-test-commit-v8-linux/169/ |
As expected run was clean thanks @targos. |
The test targets expect that V8 is built in deps/v8/out Ref: nodejs#7477 PR-URL: nodejs#7482 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: James M Snell <[email protected]>
Without this it would always compile Release and Debug builds. Ref: nodejs#7477 PR-URL: nodejs#7482 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: James M Snell <[email protected]>
The test targets expect that V8 is built in deps/v8/out Ref: #7477 PR-URL: #7482 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: James M Snell <[email protected]>
Without this it would always compile Release and Debug builds. Ref: #7477 PR-URL: #7482 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: James M Snell <[email protected]>
The test targets expect that V8 is built in deps/v8/out Ref: #7477 PR-URL: #7482 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: James M Snell <[email protected]>
Without this it would always compile Release and Debug builds. Ref: #7477 PR-URL: #7482 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: James M Snell <[email protected]>
The test targets expect that V8 is built in deps/v8/out Ref: #7477 PR-URL: #7482 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: James M Snell <[email protected]>
Without this it would always compile Release and Debug builds. Ref: #7477 PR-URL: #7482 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: James M Snell <[email protected]>
The test targets expect that V8 is built in deps/v8/out Ref: #7477 PR-URL: #7482 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: James M Snell <[email protected]>
Without this it would always compile Release and Debug builds. Ref: #7477 PR-URL: #7482 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: James M Snell <[email protected]>
The test targets expect that V8 is built in deps/v8/out Ref: #7477 PR-URL: #7482 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: James M Snell <[email protected]>
Without this it would always compile Release and Debug builds. Ref: #7477 PR-URL: #7482 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: James M Snell <[email protected]>
The test targets expect that V8 is built in deps/v8/out Ref: #7477 PR-URL: #7482 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: James M Snell <[email protected]>
Without this it would always compile Release and Debug builds. Ref: #7477 PR-URL: #7482 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: James M Snell <[email protected]>
https://ci.nodejs.org/job/node-test-commit-v8-linux/nodes=benchmark,v8test=v8test/164/console
and many others
The text was updated successfully, but these errors were encountered: