Repository navigation
Flaky test-worker-arraybuffer-zerofill with V8 12.2 #52274
Description
Activity
- added 2 commits that reference this issue
on Mar 30, 2024 @addaleax ... in test-worker-arraybuffer-zerofill.js... do you happen to remember why the test needed to allocate such huge buffers so often?
function allocBuffers() { Buffer.allocUnsafe(32 * 1024 * 1024); } const interval = setInterval(allocBuffers, 0);
I think this is what is leading to the timeout flakiness in the test.
This file was last changed five years ago so I'll understand if you don't remember ;-)
Btw, I'm assuming it's to ensure that the allocation is expensive enough to ensure that it is likely still running when the other thread allocates?
- added a commit that references this issue
on Sep 12, 2024 - added 4 commits that reference this issue
on Sep 22, 2024 This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 240 days).
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.
Test
test-worker-arraybuffer-zerofillPlatform
No response
Console output
Build links
Additional information
test-worker-arraybuffer-zerofill: this could be a real bug, or some timing assumptions being broken/messages getting lost (which may also be a real bug). We can mark it as flaky for now, and add some logs in the test to help debugging.Originally posted by @joyeecheung in #51362 (comment)