We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://github.com/servo/servo/actions/runs/8865818832/job/24343044922#step:8:2419
I suspect it's from web-platform-tests/wpt#45848
▶ TIMEOUT [expected OK] /fetch/api/crashtests/huge-fetch.any.html
but it only happens when doing flaky detection (could be that python does not run GC and when we run huge-response.py for the second time we get OOM).
Temporary solution could be to just disable running this test.
The text was updated successfully, but these errors were encountered:
This seems reasonable to me.
Sorry, something went wrong.
Disable huge-fetch test
765b942
for #32168
/fetch/api/crashtests/huge-fetch.any.js
Disable /fetch/api/crashtests/huge-fetch.any.js (#32188)
f6dc09c
* Disable huge-fetch test for #32168 * Disable huge-fetch on layout 2013 * Add issue link
Successfully merging a pull request may close this issue.
https://github.com/servo/servo/actions/runs/8865818832/job/24343044922#step:8:2419
I suspect it's from web-platform-tests/wpt#45848
but it only happens when doing flaky detection (could be that python does not run GC and when we run huge-response.py for the second time we get OOM).
Temporary solution could be to just disable running this test.
The text was updated successfully, but these errors were encountered: