Revision 491a02ce6f091db542aed561e3d984b0a18f4188 authored by fergald on 04 April 2018, 22:12:43 UTC, committed by GitHub on 04 April 2018, 22:12:43 UTC
I don't know how I got into this situation (probably hit ctrl-C at the wrong time) but I did and it was unclear how to get out. It presents as a ValueError with no useful info. Update the code to handle ValueError to log a warning and cause a full regen of the manifest. Also reported in https://crbug.com/822041
1 parent 47d7cdf
WorkerGlobalScope_setInterval.htm
<!DOCTYPE html>
<title> WorkerGlobalScope API: setInterval() </title>
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<div id=log></div>
<script>
async_test(function(t) {
var result = [];
var worker = new Worker('./support/Timer.js');
worker.onmessage = t.step_func(function(e) {
result.push(e.data);
if (result.length == 3) {
assert_array_equals(result, ["hello", "worker", "worker"]);
worker.onmessage = t.unreached_func('Unexpected message event');
setTimeout(t.step_func_done(), 100);
}
});
worker.postMessage("IntervalHandler");
});
</script>
Computing file changes ...
