-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
deps: V8: backport 4263f8a5e8e0 #35650
Conversation
re: #35196 (comment) I originally opened the above PR updating the error messages. That was instead landed upstream. This backport adds those changes and closes out #35196 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
some tiny issues with conflict resolution
deps/v8/test/cctest/interpreter/bytecode_expectations/PrivateMethodAccess.golden
Show resolved
Hide resolved
deps/v8/test/cctest/interpreter/bytecode_expectations/PrivateMethodAccess.golden
Show resolved
Hide resolved
deps/v8/test/cctest/interpreter/bytecode_expectations/PrivateAccessorAccess.golden
Outdated
Show resolved
Hide resolved
deps/v8/test/cctest/interpreter/bytecode_expectations/PrivateAccessorAccess.golden
Outdated
Show resolved
Hide resolved
deps/v8/test/cctest/interpreter/bytecode_expectations/PrivateAccessorAccess.golden
Outdated
Show resolved
Hide resolved
deps/v8/test/cctest/interpreter/bytecode_expectations/PrivateAccessorAccess.golden
Outdated
Show resolved
Hide resolved
@devsnek any idea why the V8 tests are failing? |
The failures are in files that I touched (fixed merge conflicts). Curious if it is a white space thing or similar.
|
/cc @nodejs/v8-update |
I believe |
678b58e
to
eb1aac1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM if we can get the V8 CI to pass
This comment has been minimized.
This comment has been minimized.
@Trott the issue with CI is that the .golden files need to be regenerated and afaict there is no easy way for us to do this. @devsnek was looking into this, and I believe chatted with @joyeecheung about it to. Maybe someone from @nodejs/v8-update would know how to help. |
Yes you need to remove the whitespace changes. |
deps/v8/test/cctest/interpreter/bytecode_expectations/PrivateAccessorAccess.golden
Outdated
Show resolved
Hide resolved
Looks like the CI jobs are still failing because of git issues
|
deps/v8/test/cctest/interpreter/bytecode_expectations/PrivateAccessorAccess.golden
Outdated
Show resolved
Hide resolved
deps/v8/test/cctest/interpreter/bytecode_expectations/PrivateMethodAccess.golden
Outdated
Show resolved
Hide resolved
deps/v8/test/cctest/interpreter/bytecode_expectations/PrivateMethodAccess.golden
Outdated
Show resolved
Hide resolved
deps/v8/test/cctest/interpreter/bytecode_expectations/PrivateAccessorAccess.golden
Outdated
Show resolved
Hide resolved
Original commit message: parser: better error message for await+tla Bug: v8:9344, v8:6513 Change-Id: I1854e483515e7da99192367b6764a0ec7c8b41d9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2411687 Reviewed-by: Marja Hölttä <marja@chromium.org> Commit-Queue: Gus Caplan <snek@chromium.org> Cr-Commit-Position: refs/heads/master@{#70099} Refs: v8/v8@4263f8a
c7cabcf
to
ff9c811
Compare
@joyeecheung it looks like the updates to the golden files from the original CL got lost when we updated V8 on master. I've re-applied the changes edit: Another crack at V8-CI https://ci.nodejs.org/job/node-test-commit-v8-linux/3495/ |
I did a rebaseline locally and this is the patch I get (compared to the state after this force push) and it passes the cctest locally. Should I update this branch? See diff
|
Original commit message: parser: better error message for await+tla Bug: v8:9344, v8:6513 Change-Id: I1854e483515e7da99192367b6764a0ec7c8b41d9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2411687 Reviewed-by: Marja Hölttä <marja@chromium.org> Commit-Queue: Gus Caplan <snek@chromium.org> Cr-Commit-Position: refs/heads/master@{#70099} Refs: v8/v8@4263f8a PR-URL: #35650 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Myles Borins <myles.borins@gmail.com>
Original commit message: parser: better error message for await+tla Bug: v8:9344, v8:6513 Change-Id: I1854e483515e7da99192367b6764a0ec7c8b41d9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2411687 Reviewed-by: Marja Hölttä <marja@chromium.org> Commit-Queue: Gus Caplan <snek@chromium.org> Cr-Commit-Position: refs/heads/master@{#70099} Refs: v8/v8@4263f8a PR-URL: #35650 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Myles Borins <myles.borins@gmail.com>
Original commit message:
Refs: v8/v8@4263f8a
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes