-
-
Notifications
You must be signed in to change notification settings - Fork 31.7k
test-blob-slice-with-large-size
is flaky
#57235
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
Comments
/cc @nodejs/platform-smartos |
This is now flaking many Windows tests and somehow it's relatively recent (starting from May 16 -perhaps something landed around that time made it a lot more flaky). In the latest report https://github.com/nodejs/reliability/blob/main/reports/2025-05-18.md this has failed 17 PRs out of the last 100 CI runs |
In #58379, this test has failed 6 of 8 Windows CI runs and is still blocking the PR. |
I think it's just the test not being written in a way that's robust enough to skip when there's not enough memory. Fix in #58414 |
The test only cares about whether a size outside the range of the 32-bit signed integers works with Blob.prototype.slice(). If it fails due to allocation failure when the system does not have enough memory, the test should just be skipped. The test previously only skipped the test when the allocation failure happens during allocation of the buffer source, but it could also happen during Blob.prototype.slice(). PR-URL: #58414 Fixes: #57235 Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Tobias Nießen <[email protected]> Reviewed-By: LiviaMedeiros <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Stefan Stojanovic <[email protected]>
Test
test-blob-slice-with-large-size
Platform
SmartOS
Console output
Build links
Additional information
It seems to reproduce quite rarely
The text was updated successfully, but these errors were encountered: