--- /b/rr/tmp0ECq6P/w/layout-test-results/virtual/mojo-loading/http/tests/streams/writable-streams/aborting.https-expected.txt
+++ /b/rr/tmp0ECq6P/w/layout-test-results/virtual/mojo-loading/http/tests/streams/writable-streams/aborting.https-actual.txt
@@ -42,6 +42,17 @@
 PASS WritableStream if sink's abort throws, for an abort performed during a write, the promise returned by ws.abort() rejects 
 PASS Aborting a WritableStream passes through the given reason 
 PASS Aborting a WritableStream puts it in an errored state, with a TypeError as the stored error 
+PASS Aborting a WritableStream should cause the writer's unsettled ready promise to reject 
+PASS Aborting a WritableStream should cause the writer's fulfilled ready promise to reset to a rejected one 
+PASS abort() on a released writer rejects 
+PASS Aborting a WritableStream immediately prevents future writes 
+PASS Aborting a WritableStream prevents further writes after any that are in progress 
+PASS Fulfillment value of ws.abort() call must be undefined even if the underlying sink returns a non-undefined value 
+PASS WritableStream if sink's abort throws, the promise returned by writer.abort() rejects 
+PASS WritableStream if sink's abort throws, the promise returned by ws.abort() rejects 
+PASS WritableStream if sink's abort throws, for an abort performed during a write, the promise returned by ws.abort() rejects 
+PASS Aborting a WritableStream passes through the given reason 
+PASS Aborting a WritableStream puts it in an errored state, with a TypeError as the stored error 
 PASS Aborting a WritableStream causes any outstanding write() promises to be rejected with a TypeError 
 PASS Closing but then immediately aborting a WritableStream causes the stream to error 
 PASS Closing a WritableStream and aborting it while it closes causes the stream to error 
@@ -61,17 +72,6 @@
 PASS writer.ready should reject on controller error without waiting for underlying write 
 PASS releaseLock() while aborting should reject the original closed promise 
 PASS releaseLock() during delayed async abort() should create a new rejected closed promise 
-PASS Aborting a WritableStream should cause the writer's unsettled ready promise to reject 
-PASS Aborting a WritableStream should cause the writer's fulfilled ready promise to reset to a rejected one 
-PASS abort() on a released writer rejects 
-PASS Aborting a WritableStream immediately prevents future writes 
-PASS Aborting a WritableStream prevents further writes after any that are in progress 
-PASS Fulfillment value of ws.abort() call must be undefined even if the underlying sink returns a non-undefined value 
-PASS WritableStream if sink's abort throws, the promise returned by writer.abort() rejects 
-PASS WritableStream if sink's abort throws, the promise returned by ws.abort() rejects 
-PASS WritableStream if sink's abort throws, for an abort performed during a write, the promise returned by ws.abort() rejects 
-PASS Aborting a WritableStream passes through the given reason 
-PASS Aborting a WritableStream puts it in an errored state, with a TypeError as the stored error 
 PASS Aborting a WritableStream causes any outstanding write() promises to be rejected with a TypeError 
 PASS Closing but then immediately aborting a WritableStream causes the stream to error 
 PASS Closing a WritableStream and aborting it while it closes causes the stream to error 
