Repository navigation
wpt/test-structured-clone is flaky #49852
Description
Activity
It seems strange that this is a flake, the error should be thrown by V8 when the object cannot be deserialized somehow.
Unfortunately we don't have a lot of information about where the exception comes from, the JS stack is lost due to asynchronicity, maybe we can tweak the wpt harness a bit to capture the stack (not sure if it's already lost by then though)
cc @legendecas as you've recently touched the serdes part
I wonder if could be related to #49713 compare_Blob function uses Response().arrayBuffer() which internally would be using streams to get the data. will try to reproduce this
That could be a cause, we can try stress-testing a revert
Does it not seem to be happening on macos? I tried locally with --repeat 1000 but no reproduction would be weird if this was os specific
Sorry for the delay, I was on a trip last week. I'm going to take a look as soon as possible.
Test
wpt/test-structured-clone
Platform
Linux ARM64, Linux x64, Windows
Console output
wpt/test-structured-cloneAdditional information
nodejs/reliability#675