-
Notifications
You must be signed in to change notification settings - Fork 4.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
[browser][MT] Assert failed: Cannot find Promise for JSHandle -2 #98406
Comments
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsError Blob{
"ErrorMessage": "Cannot find Promise for JSHandle -2",
"BuildRetry": false,
"ErrorPattern": "",
"ExcludeConsoleLog": false
} Reproduction StepsBuild: https://dev.azure.com/dnceng-public/public/_build/results?buildId=565532
|
|
|
maybe this is synchronous GC of the handle before resolve |
I opened #98721 so this variant would also show up green in analysis |
@pavelsavara I don't see a failure of 'Cannot find Promise for JSHandle' outside the JS interop tests where the JsHandle value isn't -2, the GCHandle failure is different and is much more limited. |
Here's a fresh hit in an unrelated PR for main: #98885
Output (expand)
|
Current theory :
|
I will re-open it so that we could see if that helped. If so I will close it in about a week |
There haven't been any occurrences of the issue in the last two days. I will provide updates here in case of any changes. |
Note, that @lewing disabled the most offending test here #98951 I also made 2 attempts to fix it, the later merged just moment ago
Let's keep this open and eventually enable the test again by merging #99000 |
Error Blob
Reproduction Steps
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=565532
Log
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=565532
Error message validated:
[Cannot find Promise for JSHandle
]Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 2/14/2024 10:13:57 AM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: