Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(159)

Side by Side Diff: third_party/WebKit/LayoutTests/http/tests/streams/writable-streams/aborting.https-expected.txt

Issue 2766823003: Fix testharness result parsing, make "Harness error" count as failure. (Closed)
Patch Set: One more test with nondeterministic message order Created 3 years, 9 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
OLDNEW
(Empty)
1 This is a testharness.js-based test.
2 Harness Error. harness_status.status = 1 , harness_status.message = 30 duplicate test names: "Aborting a WritableStream should cause the writer's unsettled read y promise to reject", "Aborting a WritableStream should cause the writer's fulfi lled ready promise to reset to a rejected one", "abort() on a released writer re jects", "Aborting a WritableStream immediately prevents future writes", "Abortin g a WritableStream prevents further writes after any that are in progress", "Ful fillment value of ws.abort() call must be undefined even if the underlying sink returns a non-undefined value", "WritableStream if sink's abort throws, the prom ise returned by writer.abort() rejects", "WritableStream if sink's abort throws, the promise returned by ws.abort() rejects", "WritableStream if sink's abort th rows, for an abort performed during a write, the promise returned by ws.abort() rejects", "Aborting a WritableStream passes through the given reason", "Aborting a WritableStream puts it in an errored state, with a TypeError as the stored er ror", "Aborting a WritableStream causes any outstanding write() promises to be r ejected with a TypeError", "Closing but then immediately aborting a WritableStre am causes the stream to error", "Closing a WritableStream and aborting it while it closes causes the stream to error", "Aborting a WritableStream after it is cl osed is a no-op", "WritableStream should NOT call underlying sink's close if no abort is supplied (historical)", "returning a thenable from abort() should work" , ".closed should not resolve before fulfilled write()", ".closed should not res olve before rejected write(); write() error should overwrite abort() error", "wr ites should be satisfied in order when aborting", "writes should be satisfied in order after rejected write when aborting", "close() should use error from under lying write() on abort", "underlying abort() should not be called until underlyi ng write() completes", "underlying abort() should not be called if underlying cl ose() has started", "if underlying close() has started and then rejects, the abo rt() and close() promises should reject with the underlying close rejection reas on", "underlying abort() should be called while closing if underlying close() ha s not started yet", "writer close() promise should resolve before abort() promis e", "writer.ready should reject on controller error without waiting for underlyi ng write", "releaseLock() while aborting should reject the original closed promi se", "releaseLock() during delayed async abort() should create a new rejected cl osed promise"
3 PASS Aborting a WritableStream should cause the writer's unsettled ready promise to reject
4 PASS Aborting a WritableStream should cause the writer's fulfilled ready promise to reset to a rejected one
5 PASS abort() on a released writer rejects
6 PASS Aborting a WritableStream immediately prevents future writes
7 PASS Aborting a WritableStream prevents further writes after any that are in pro gress
8 PASS Fulfillment value of ws.abort() call must be undefined even if the underlyi ng sink returns a non-undefined value
9 PASS WritableStream if sink's abort throws, the promise returned by writer.abort () rejects
10 PASS WritableStream if sink's abort throws, the promise returned by ws.abort() r ejects
11 PASS WritableStream if sink's abort throws, for an abort performed during a writ e, the promise returned by ws.abort() rejects
12 PASS Aborting a WritableStream passes through the given reason
13 PASS Aborting a WritableStream puts it in an errored state, with a TypeError as the stored error
14 PASS Aborting a WritableStream causes any outstanding write() promises to be rej ected with a TypeError
15 PASS Closing but then immediately aborting a WritableStream causes the stream to error
16 PASS Closing a WritableStream and aborting it while it closes causes the stream to error
17 PASS Aborting a WritableStream after it is closed is a no-op
18 PASS WritableStream should NOT call underlying sink's close if no abort is suppl ied (historical)
19 PASS returning a thenable from abort() should work
20 PASS .closed should not resolve before fulfilled write()
21 PASS .closed should not resolve before rejected write(); write() error should ov erwrite abort() error
22 PASS writes should be satisfied in order when aborting
23 PASS writes should be satisfied in order after rejected write when aborting
24 PASS close() should use error from underlying write() on abort
25 PASS underlying abort() should not be called until underlying write() completes
26 PASS underlying abort() should not be called if underlying close() has started
27 PASS if underlying close() has started and then rejects, the abort() and close() promises should reject with the underlying close rejection reason
28 PASS underlying abort() should be called while closing if underlying close() has not started yet
29 PASS writer close() promise should resolve before abort() promise
30 PASS writer.ready should reject on controller error without waiting for underlyi ng write
31 PASS releaseLock() while aborting should reject the original closed promise
32 PASS releaseLock() during delayed async abort() should create a new rejected clo sed promise
33 PASS Untitled
34 PASS Aborting a WritableStream should cause the writer's unsettled ready promise to reject
35 PASS Aborting a WritableStream should cause the writer's fulfilled ready promise to reset to a rejected one
36 PASS abort() on a released writer rejects
37 PASS Aborting a WritableStream immediately prevents future writes
38 PASS Aborting a WritableStream prevents further writes after any that are in pro gress
39 PASS Fulfillment value of ws.abort() call must be undefined even if the underlyi ng sink returns a non-undefined value
40 PASS WritableStream if sink's abort throws, the promise returned by writer.abort () rejects
41 PASS WritableStream if sink's abort throws, the promise returned by ws.abort() r ejects
42 PASS WritableStream if sink's abort throws, for an abort performed during a writ e, the promise returned by ws.abort() rejects
43 PASS Aborting a WritableStream passes through the given reason
44 PASS Aborting a WritableStream puts it in an errored state, with a TypeError as the stored error
45 PASS Aborting a WritableStream causes any outstanding write() promises to be rej ected with a TypeError
46 PASS Closing but then immediately aborting a WritableStream causes the stream to error
47 PASS Closing a WritableStream and aborting it while it closes causes the stream to error
48 PASS Aborting a WritableStream after it is closed is a no-op
49 PASS WritableStream should NOT call underlying sink's close if no abort is suppl ied (historical)
50 PASS returning a thenable from abort() should work
51 PASS .closed should not resolve before fulfilled write()
52 PASS .closed should not resolve before rejected write(); write() error should ov erwrite abort() error
53 PASS writes should be satisfied in order when aborting
54 PASS writes should be satisfied in order after rejected write when aborting
55 PASS close() should use error from underlying write() on abort
56 PASS underlying abort() should not be called until underlying write() completes
57 PASS underlying abort() should not be called if underlying close() has started
58 PASS if underlying close() has started and then rejects, the abort() and close() promises should reject with the underlying close rejection reason
59 PASS underlying abort() should be called while closing if underlying close() has not started yet
60 PASS writer close() promise should resolve before abort() promise
61 PASS writer.ready should reject on controller error without waiting for underlyi ng write
62 PASS releaseLock() while aborting should reject the original closed promise
63 PASS releaseLock() during delayed async abort() should create a new rejected clo sed promise
64 PASS Aborting a WritableStream should cause the writer's unsettled ready promise to reject
65 PASS Aborting a WritableStream should cause the writer's fulfilled ready promise to reset to a rejected one
66 PASS abort() on a released writer rejects
67 PASS Aborting a WritableStream immediately prevents future writes
68 PASS Aborting a WritableStream prevents further writes after any that are in pro gress
69 PASS Fulfillment value of ws.abort() call must be undefined even if the underlyi ng sink returns a non-undefined value
70 PASS WritableStream if sink's abort throws, the promise returned by writer.abort () rejects
71 PASS WritableStream if sink's abort throws, the promise returned by ws.abort() r ejects
72 PASS WritableStream if sink's abort throws, for an abort performed during a writ e, the promise returned by ws.abort() rejects
73 PASS Aborting a WritableStream passes through the given reason
74 PASS Aborting a WritableStream puts it in an errored state, with a TypeError as the stored error
75 PASS Aborting a WritableStream causes any outstanding write() promises to be rej ected with a TypeError
76 PASS Closing but then immediately aborting a WritableStream causes the stream to error
77 PASS Closing a WritableStream and aborting it while it closes causes the stream to error
78 PASS Aborting a WritableStream after it is closed is a no-op
79 PASS WritableStream should NOT call underlying sink's close if no abort is suppl ied (historical)
80 PASS returning a thenable from abort() should work
81 PASS .closed should not resolve before fulfilled write()
82 PASS .closed should not resolve before rejected write(); write() error should ov erwrite abort() error
83 PASS writes should be satisfied in order when aborting
84 PASS writes should be satisfied in order after rejected write when aborting
85 PASS close() should use error from underlying write() on abort
86 PASS underlying abort() should not be called until underlying write() completes
87 PASS underlying abort() should not be called if underlying close() has started
88 PASS if underlying close() has started and then rejects, the abort() and close() promises should reject with the underlying close rejection reason
89 PASS underlying abort() should be called while closing if underlying close() has not started yet
90 PASS writer close() promise should resolve before abort() promise
91 PASS writer.ready should reject on controller error without waiting for underlyi ng write
92 PASS releaseLock() while aborting should reject the original closed promise
93 PASS releaseLock() during delayed async abort() should create a new rejected clo sed promise
94 PASS Aborting a WritableStream should cause the writer's unsettled ready promise to reject
95 PASS Aborting a WritableStream should cause the writer's fulfilled ready promise to reset to a rejected one
96 PASS abort() on a released writer rejects
97 PASS Aborting a WritableStream immediately prevents future writes
98 PASS Aborting a WritableStream prevents further writes after any that are in pro gress
99 PASS Fulfillment value of ws.abort() call must be undefined even if the underlyi ng sink returns a non-undefined value
100 PASS WritableStream if sink's abort throws, the promise returned by writer.abort () rejects
101 PASS WritableStream if sink's abort throws, the promise returned by ws.abort() r ejects
102 PASS WritableStream if sink's abort throws, for an abort performed during a writ e, the promise returned by ws.abort() rejects
103 PASS Aborting a WritableStream passes through the given reason
104 PASS Aborting a WritableStream puts it in an errored state, with a TypeError as the stored error
105 PASS Aborting a WritableStream causes any outstanding write() promises to be rej ected with a TypeError
106 PASS Closing but then immediately aborting a WritableStream causes the stream to error
107 PASS Closing a WritableStream and aborting it while it closes causes the stream to error
108 PASS Aborting a WritableStream after it is closed is a no-op
109 PASS WritableStream should NOT call underlying sink's close if no abort is suppl ied (historical)
110 PASS returning a thenable from abort() should work
111 PASS .closed should not resolve before fulfilled write()
112 PASS .closed should not resolve before rejected write(); write() error should ov erwrite abort() error
113 PASS writes should be satisfied in order when aborting
114 PASS writes should be satisfied in order after rejected write when aborting
115 PASS close() should use error from underlying write() on abort
116 PASS underlying abort() should not be called until underlying write() completes
117 PASS underlying abort() should not be called if underlying close() has started
118 PASS if underlying close() has started and then rejects, the abort() and close() promises should reject with the underlying close rejection reason
119 PASS underlying abort() should be called while closing if underlying close() has not started yet
120 PASS writer close() promise should resolve before abort() promise
121 PASS writer.ready should reject on controller error without waiting for underlyi ng write
122 PASS releaseLock() while aborting should reject the original closed promise
123 PASS releaseLock() during delayed async abort() should create a new rejected clo sed promise
124 Harness: the test ran to completion.
125
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698