Implement suspend() and resume() for OfflineAudioContext

third_party/WebKit/LayoutTests/webaudio/offlineaudiocontext-suspend-resume-sequence-expected.txt

Index: third_party/WebKit/LayoutTests/webaudio/offlineaudiocontext-suspend-resume-sequence-expected.txt
diff --git a/third_party/WebKit/LayoutTests/webaudio/offlineaudiocontext-suspend-resume-sequence-expected.txt b/third_party/WebKit/LayoutTests/webaudio/offlineaudiocontext-suspend-resume-sequence-expected.txt
new file mode 100644
index 0000000000000000000000000000000000000000..eca9aad53e44c21352ac4c7fcc8d23465d44706b
--- /dev/null
+++ b/third_party/WebKit/LayoutTests/webaudio/offlineaudiocontext-suspend-resume-sequence-expected.txt
@@ -0,0 +1,16 @@
+Test OfflineAudioContext.resume() and OfflineAudioContext.suspend() with the timed sequence.
+
+On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE".
+
+
+PASS The actual resolution order of the suspend 5 (0.00 sec.) is equal to 0.

[Raymond Toy, 2015/10/21 18:22:45]

I think it would be really helpful if you printed out PASS when each suspend is
called.  Then you can see the actual order of the calls to suspend, and then the
messages here and below make obvious sense that they're suspended in time order.

[hongchan, 2015/10/22 18:23:48]

Done.

+PASS The actual resolution order of the suspend 0 (0.25 sec.) is equal to 1.
+PASS The actual resolution order of the suspend 3 (0.50 sec.) is equal to 2.
+PASS The actual resolution order of the suspend 1 (0.75 sec.) is equal to 3.
+PASS The actual resolution order of the suspend 2 (1.00 sec.) is equal to 4.
+PASS The actual resolution order of the suspend 4 (1.25 sec.) is equal to 5.
+PASS The actual resolution order of the suspend 6 (1.75 sec.) is equal to 6.
+PASS successfullyParsed is true
+
+TEST COMPLETE
+