-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
script: when fetching a worker script abort if response status is not ok #39468
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
Conversation
Signed-off-by: Gae24 <96017547+Gae24@users.noreply.github.com>
|
Question, can it happens that the resulting bytes are zero? In which case we should do the same. There are three other usages of After a quick check of the spec, we should do the same inside |
|
🔨 Triggering try run (#17978573011) for Linux (WPT) |
|
Test results for linux-wpt from try job (#17978573011): Flaky unexpected result (21)
Stable unexpected results that are known to be intermittent (25)
Stable unexpected results (1)
|
|
|
I've run this test locally with a debug build a couple times and failed everytime. |
Does it fail with an |
Oh, I interpreted the result wrong. |
Signed-off-by: Gae24 <96017547+Gae24@users.noreply.github.com>
jdm
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
|
Let's do that in a new PR! |
… ok (servo#39468) According to [spec](https://html.spec.whatwg.org/multipage/webappapis.html#fetch-a-classic-worker-script) we should abort if the response status is not ok. Testing: Check tests listed inside issue are not intermittent anymore Fixes: servo#39413 Fixes: servo#22991 --------- Signed-off-by: Gae24 <96017547+Gae24@users.noreply.github.com>
According to spec we should abort if the response status is not ok.
Testing: Check tests listed inside issue are not intermittent anymore
Fixes: #39413
Fixes: #22991