Uh oh!
There was an error while loading. Please reload this page.
[wasm] Bump chrome for testing - linux: 120.0.6099.71, windows: 120.0.6099.71 - #95832
Conversation
ghost
commented
Dec 10, 2023
Tagging subscribers to 'arch-wasm': @lewing Issue Detailsnull
|
radical
commented
Dec 11, 2023
Cc @thaystg@ilonatommy debugger test failures |
It seems objectId changed format. Now the test is sending {
"functionDeclaration": "function(){const e={__proto__:this.__proto__},t=Object.getOwnPropertyNames(this);for(let r=0;r<t.length;++r){const n=t[r],i=n>>>0;if(String(i>>>0)===n&&i>>>0!=4294967295)continue;const a=Object.getOwnPropertyDescriptor(this,n);a&&Object.defineProperty(e,n,a)}return e}",
"objectId": "7794664587706423672.1.8"
}so edit: they can be negative as well, another example: |
radical
commented
Dec 11, 2023
That sounds like some error/failure caused this weird id? |
radical
commented
Dec 11, 2023
DebuggerTests.CallFunctionOnTests.CheckVSCodeTestFunction1: |
ilonatommy
commented
Dec 12, 2023
It's not an error, the quoted structure comes from We can fix it and keep fixing it each time the protocol changes on next updates. |
radical
commented
Dec 12, 2023
The failure is not due to the objectId though. I was pointing to that as a possible clue. The failure is: |
radical
commented
Dec 13, 2023
Taking a look at the failure. |
radical
commented
Dec 13, 2023
Disabling the test, and opened #95950 . |
radical
commented
Dec 13, 2023
Failure is a known issue. |
No description provided.