Backed out changeset c6cf679e8f08 (bug 1773237) for causing bc failures on Promise-inl.h. CLOSED TREE

This commit is contained in:
Marian-Vasile Laza
2022-10-06 21:34:22 +03:00
parent dc3acd3063
commit 6e84b31e91
3 changed files with 0 additions and 17 deletions

View File

@@ -151,11 +151,6 @@ void FetchStreamReader::CloseAndRelease(JSContext* aCx, nsresult aStatus) {
MOZ_KnownLive(mReader)->Cancel(aCx, errorValue, ignoredError); MOZ_KnownLive(mReader)->Cancel(aCx, errorValue, ignoredError);
NS_WARNING_ASSERTION(!ignoredError.Failed(), NS_WARNING_ASSERTION(!ignoredError.Failed(),
"Failed to cancel stream during close and release"); "Failed to cancel stream during close and release");
if (ignoredResultPromise) {
bool setSettled = ignoredResultPromise->SetSettledPromiseIsHandled();
NS_WARNING_ASSERTION(setSettled, "Failed to settle cancel promise");
(void)setSettled;
}
} }
// We don't want to propagate exceptions during the cleanup. // We don't want to propagate exceptions during the cleanup.

View File

@@ -1,11 +0,0 @@
// This test fails if there is an unhandled promise rejection
var stream = new ReadableStream({
pull() {
return Promise.reject("foobar");
},
});
var response = new Response(stream);
var text = response.text().then(
() => {},
e => {}
);

View File

@@ -19,4 +19,3 @@ skip-if =
tsan # Causes claim expired errors; see Bug 1770170. tsan # Causes claim expired errors; see Bug 1770170.
run-sequentially = very high failure rate in parallel run-sequentially = very high failure rate in parallel
[too-big-array-buffer.js] [too-big-array-buffer.js]
[bug-1773237.js]