Uh oh!
There was an error while loading. Please reload this page.
deps: update V8 to 11.6 - #48710
Conversation
nodejs-github-bot
commented
Jul 9, 2023
Review requested:
|
targos
commented
Jul 9, 2023
@nodejs/cpp-reviewers |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
targos
commented
Jul 10, 2023
V8 CI is broken (looks like we're still trying to run it with Python 2.7) |
nodejs-github-bot
commented
Jul 10, 2023
richardlau
commented
Jul 10, 2023
Yes, also reported in #48660 (comment). I tried a quick patch to try to get the CI to use Python 3 over the weekend and it looks like we're missing some required Python modules on the Python 3 installation: https://ci.nodejs.org/job/node-test-commit-v8-linux/5435/ |
Original commit message: Fix mistake in the skip branch of test/mjsunit/regress-1320641.js It was doing a `string.test(regex)` which was wrong. It's supposed to be `regex.test(string)`. It wasn't caught in the CI because the skip path is not normally taken in the V8 CI. Change-Id: Id1bdab5bbc41968bba8adc1cb3664e8f95fb5d72 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4697855 Commit-Queue: Joyee Cheung <joyee@igalia.com> Reviewed-by: Nico Hartmann <nicohartmann@chromium.org> Cr-Commit-Position: refs/heads/main@{#89044} Refs: v8/v8@9f4b769 PR-URL: nodejs#48830 Refs: v8/v8@c1a54d5 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Jiawen Geng <technicalcute@gmail.com> Reviewed-By: Debadree Chatterjee <debadree333@gmail.com>
Original commit message: [cppgc] expose wrapper descriptor on CppHeap This makes it possible for embedders to: 1. Avoid creating wrapper objects that happen to have a layout that leads V8 to consider the object cppgc-managed while it's not. Refs: nodejs#43521 2. Create cppgc-managed wrapper objects when they do not own the CppHeap. Refs: nodejs#45704 Bug: v8:13960 Change-Id: If31f4d56c5ead59dc0d56f937494d23d631f7438 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4598833 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#88490} Refs: v8/v8@9327503 PR-URL: nodejs#48660 Reviewed-By: Chengzhong Wu <legendecas@gmail.com> Reviewed-By: Jiawen Geng <technicalcute@gmail.com>
Accept a new `step` break message.
`--no-harmony-sharedarraybuffer` was removed from V8 but it's still possible to disable the feature with `--enable-sharedarraybuffer-per-context`.
targos
commented
Jul 31, 2023
cdebfb6 fixed it on my mac. |
targos
commented
Aug 1, 2023
We're back to the zlib-related error: https://ci.nodejs.org/job/node-test-commit-smartos/50446/nodes=smartos20-64/console |
targos
commented
Aug 7, 2023
/cc @nodejs/tsc This is essentially blocked on one compiler issue that I don't know how to handle (see above comment). |
gengjiawen
commented
Aug 16, 2023
I suppose #47493 should help in this case. |
targos
commented
Aug 16, 2023
Yeah, but that PR is unfortunately stale. |
targos
commented
Sep 16, 2023
Replaced by #49639 |
No description provided.