Conversation
|
Tests on nodejs/node#32116 are failing with those changes, and I don't think it helped supress any build warnings (but then again, we're getting so many warnings there it's hard to tell). Should this work on 8.1? |
The failed may not related to this change. Github action still show previous already failed case.
It do fix 5 warnings, you can see warning https://github.com/nodejs/node-v8/runs/481711528 (search crbug), which I notice the bug in first place. Also @addaleax put todos in related code. Details../deps/v8/include/v8.h:5169:8: note: declared here
bool IsExternal() const;
^~~~~~~~~~
../src/js_native_api_v8.cc:2725:50: warning: ‘void v8::ArrayBuffer::Externalize(const std::shared_ptr<v8::BackingStore>&)’ is deprecated: This will be removed together with IsExternal. [-Wdeprecated-declarations]
buffer->Externalize(buffer->GetBackingStore());
^
In file included from ../src/util.h:31:0,
from ../src/aliased_buffer.h:7,
from ../src/env-inl.h:27,
from ../src/js_native_api_v8.cc:5:
../deps/v8/include/v8.h:5206:8: note: declared here
void Externalize(const std::shared_ptr<BackingStore>& backing_store);
^~~~~~~~~~~
In file included from ../src/js_native_api_v8.cc:6:0:
../src/js_native_api_v8.cc: In function ‘napi_status napi_detach_arraybuffer(napi_env, napi_value)’:
../src/js_native_api_v8.cc:3189:27: warning: ‘bool v8::ArrayBuffer::IsExternal() const’ is deprecated: With v8::BackingStore externalized ArrayBuffers are the same as ordinary ArrayBuffers. See http://crbug.com/v8/9908. [-Wdeprecated-declarations]
env, it->IsExternal(), napi_detachable_arraybuffer_expected);
^
../src/js_native_api_v8.h:141:11: note: in definition of macro ‘RETURN_STATUS_IF_FALSE’
Yeap. But still @addaleax review this will more helpful (I have poor knowledge in V8). |
I reverted and the failure stopped. If I cherry-pick this commit I can reproduce the failure predictably on my machine. Bear in mind we've been on 8.2 on this repository for a while now. |
I see. Let's not include this to v8 8.1 then. |
|
I’ll take a look 👍 |
|
@mmarchini @gengjiawen Can you point me to the failing tests? When running the tests on this PR locally, 3 memory tests + test-inspector-multisession-ws fail, but the same tests also fail on the |
|
Ah, judging from the conversation above, this only fails when applied to V8 8.1? In that case, yeah, simply leaving it out of the V8 8.1 PR makes sense to me. |
Co-authored-by: Ben Noordhuis <info@bnoordhuis.nl> Co-authored-by: Michaël Zasso <targos@protonmail.com> Co-authored-by: Richard Lau <riclau@uk.ibm.com> Co-authored-by: Ujjwal Sharma <ryzokuken@igalia.com>
Original commit message:
[testrunner] delete ancient junit compatible format support
Testrunner has ancient support for JUnit compatible XML output.
This CL removes this old feature.
R=mstarzinger@chromium.org,jgruber@chromium.org,jkummerow@chromium.org
CC=machenbach@chromium.org
Bug: v8:8728
Change-Id: I7e1beb011dbaec3aa1a27398a5c52abdd778eaf0
Reviewed-on: https://chromium-review.googlesource.com/c/1430065
Reviewed-by: Jakob Gruber <jgruber@chromium.org>
Reviewed-by: Michael Starzinger <mstarzinger@chromium.org>
Commit-Queue: Tamer Tas <tmrts@chromium.org>
Cr-Commit-Position: refs/heads/master@{#59045}
Refs: v8/v8@bd019bd
Patch V8 (compiler/js-heap-broker.cc) to remove the use of an optional property, which is a fairly new C++ feature, since that requires a newer XCode version than the minimum requirement in BUILDING.md and thus breaks CI.
Fixes a compilation issue on some platforms
This should be semver-patch since actual invocation is version conditional.
There is a bug in the most recent version of VS2015 that affects v8.h and therefore prevents compilation of addons. Refs: https://stackoverflow.com/q/38378693
This reverts commit 5981fb7.
Bump minimum version of ICU needed to build node to 65. Refs: v8/v8@74bf96e
Original commit message:
Remove unnecessary export, which happens to break MSVC DLL builds.
Change-Id: I47c9211274cefd26bde6bd93aa7503e022df4357
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2042874
Reviewed-by: Ulan Degenbaev <ulan@chromium.org>
Commit-Queue: Bill Ticehurst <billti@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#66179}
Refs: v8/v8@1e36e21
Co-authored-by: Ben Noordhuis <info@bnoordhuis.nl>
These methods will be removed in V8 8.1, hence we need to stop overriding them.
This commit replaces Symbol::Name() with Symbol::Description(). Fixes: nodejs/node#30916
The {SetExpectInlineWasm} method is deprecated and non-functional since
V8 v8.1.
Thus node should stop calling it, so that it can be fully removed in a
future v8 version.
until 4c7c6f732cb607676bec1c9acb570e91ddfc507d
|
Just tried to cherry-pick it on canary-base and I'm seeing this failure: $ out/Release/node /home/mmarchini/workspace/nodejs/node-canary-base-cherrypicks/test/js-native-api/test_typedarray/test.js
assert.js:102
throw new AssertionError(obj);
^
AssertionError [ERR_ASSERTION]: Missing expected exception.
at /home/mmarchini/workspace/nodejs/node-canary-base-cherrypicks/test/js-native-api/test_typedarray/test.js:81:10
at Array.forEach (<anonymous>)
at Object.<anonymous> (/home/mmarchini/workspace/nodejs/node-canary-base-cherrypicks/test/js-native-api/test_typedarray/test.js:79:12)
at Module._compile (internal/modules/cjs/loader.js:1202:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1222:10)
at Module.load (internal/modules/cjs/loader.js:1051:32)
at Function.Module._load (internal/modules/cjs/loader.js:947:14)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:71:12)
at internal/main/run_main_module.js:17:47 {
generatedMessage: false,
code: 'ERR_ASSERTION',
actual: undefined,
expected: /A detachable arraybuffer was expected/,
operator: 'throws'
} |
e93af49 to
4f5d403
Compare
Maybe some upstream change caused this. I will try to do a little digging. |
|
Also previous v8 version on |
|
Github action also shows the only test failure is |
|
Started another CI: https://ci.nodejs.org/job/node-test-pull-request/29638/, but FWIW, the previous CI was also failing on |
|
So the test is failing because test_typedarray/test.js#L79-L84 expects Uint8Array and family to be non-detachable (because they don't have externalized memory), but since we removed // TODO(addaleax): Remove the first condition once we have V8 8.0.
RETURN_STATUS_IF_FALSE(
env, it->IsExternal(), napi_detachable_arraybuffer_expected); a call to diff --git a/test/js-native-api/test_typedarray/test.js b/test/js-native-api/test_typedarray/test.js
index 0d9594d929..f3efcc6e23 100644
--- a/test/js-native-api/test_typedarray/test.js
+++ b/test/js-native-api/test_typedarray/test.js
@@ -78,9 +78,7 @@ nonByteArrayTypes.forEach((currentType) => {
// Test detaching
arrayTypes.forEach((currentType) => {
const buffer = Reflect.construct(currentType, [8]);
- assert.throws(
- () => test_typedarray.Detach(buffer),
- /A detachable arraybuffer was expected/);
+ assert.doesNotThrow(() => test_typedarray.Detach(buffer));
});
{
const buffer = test_typedarray.External();@addaleax what do you think? |
7891c55 to
24edde6
Compare
e36a923 to
bf56857
Compare
|
Ping @addaleax |
0c74d28 to
13d7e86
Compare
|
Close in favor of nodejs/node#32358. |
Fix nodejs/node#30915
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passes