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

Side by Side Diff: third_party/WebKit/LayoutTests/http/tests/streams/writable-streams/close.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, 8 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 = 11 duplicate test names: "fulfillment value of ws.close() call must be undefined even if the underlying sink returns a non-undefined value", "when sink calls error asynchro nously while closing, the stream should become errored", "when sink calls error synchronously while closing, the stream should become errored", "when close is c alled on a WritableStream in writable state, ready should return a fulfilled pro mise", "when close is called on a WritableStream in waiting state, ready promise should be fulfilled", "when close is called on a WritableStream in waiting stat e, ready should be fulfilled immediately even if close takes a long time", "retu rning a thenable from close() should work", "releaseLock() should not change the result of sync close()", "releaseLock() should not change the result of async c lose()", "close() should set state to CLOSED even if writer has detached", "the promise returned by async abort during close should resolve"
3 PASS fulfillment value of ws.close() call must be undefined even if the underlyi ng sink returns a non-undefined value
4 PASS when sink calls error asynchronously while closing, the stream should becom e errored
5 PASS when sink calls error synchronously while closing, the stream should become errored
6 PASS when close is called on a WritableStream in writable state, ready should re turn a fulfilled promise
7 PASS when close is called on a WritableStream in waiting state, ready promise sh ould be fulfilled
8 PASS when close is called on a WritableStream in waiting state, ready should be fulfilled immediately even if close takes a long time
9 PASS returning a thenable from close() should work
10 PASS releaseLock() should not change the result of sync close()
11 PASS releaseLock() should not change the result of async close()
12 PASS close() should set state to CLOSED even if writer has detached
13 PASS the promise returned by async abort during close should resolve
14 PASS Untitled
15 PASS fulfillment value of ws.close() call must be undefined even if the underlyi ng sink returns a non-undefined value
16 PASS when sink calls error asynchronously while closing, the stream should becom e errored
17 PASS when sink calls error synchronously while closing, the stream should become errored
18 PASS when close is called on a WritableStream in writable state, ready should re turn a fulfilled promise
19 PASS when close is called on a WritableStream in waiting state, ready promise sh ould be fulfilled
20 PASS when close is called on a WritableStream in waiting state, ready should be fulfilled immediately even if close takes a long time
21 PASS returning a thenable from close() should work
22 PASS releaseLock() should not change the result of sync close()
23 PASS releaseLock() should not change the result of async close()
24 PASS close() should set state to CLOSED even if writer has detached
25 PASS the promise returned by async abort during close should resolve
26 PASS fulfillment value of ws.close() call must be undefined even if the underlyi ng sink returns a non-undefined value
27 PASS when sink calls error asynchronously while closing, the stream should becom e errored
28 PASS when sink calls error synchronously while closing, the stream should become errored
29 PASS when close is called on a WritableStream in writable state, ready should re turn a fulfilled promise
30 PASS when close is called on a WritableStream in waiting state, ready promise sh ould be fulfilled
31 PASS when close is called on a WritableStream in waiting state, ready should be fulfilled immediately even if close takes a long time
32 PASS returning a thenable from close() should work
33 PASS releaseLock() should not change the result of sync close()
34 PASS releaseLock() should not change the result of async close()
35 PASS close() should set state to CLOSED even if writer has detached
36 PASS the promise returned by async abort during close should resolve
37 PASS fulfillment value of ws.close() call must be undefined even if the underlyi ng sink returns a non-undefined value
38 PASS when sink calls error asynchronously while closing, the stream should becom e errored
39 PASS when sink calls error synchronously while closing, the stream should become errored
40 PASS when close is called on a WritableStream in writable state, ready should re turn a fulfilled promise
41 PASS when close is called on a WritableStream in waiting state, ready promise sh ould be fulfilled
42 PASS when close is called on a WritableStream in waiting state, ready should be fulfilled immediately even if close takes a long time
43 PASS returning a thenable from close() should work
44 PASS releaseLock() should not change the result of sync close()
45 PASS releaseLock() should not change the result of async close()
46 PASS close() should set state to CLOSED even if writer has detached
47 PASS the promise returned by async abort during close should resolve
48 Harness: the test ran to completion.
49
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698