script: when fetching a worker script abort if response status is not ok#39468
script: when fetching a worker script abort if response status is not ok#39468jdm merged 2 commits intoservo:mainfrom
Conversation
Signed-off-by: Gae24 <[email protected]>
|
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 <[email protected]>
|
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 <[email protected]>
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