Fix the geofencing test to not break if the promises resolve asynchronously.

LayoutTests/http/tests/geofencing/resources/worker.js

+importScripts('../../serviceworker/resources/worker-test-harness.js');
+
+promise_test(function(test) {
+    return navigator.geofencing.registerRegion(new CircularGeofencingRegion({latitude: 37.421999, longitude: -122.084015}))

[jsbell, 2014/09/11 21:13:35]

Maybe break this line (and the similarly long line in the .html?)

(Not strictly required, but doesn't hurt and the SW tests follow the 80-char
rule)

[Marijn Kruisselbrink, 2014/09/11 21:54:26]

Done. And I changed the indentation a bit as well, to match the SW layout tests
(even though these are not SW tests, but the general layouttests styleguide
seems to explicitly allow things like two space indents anywhere).

+        .then(test.unreached_func('Promise should not have resolved'))
+        .catch(function() {});
+}, 'registerRegion should fail');
+
+promise_test(function(test) {
+    return navigator.geofencing.unregisterRegion("")
+        .then(test.unreached_func('Promise should not have resolved'))
+        .catch(function() {});
+}, 'unregisterRegion should fail');
+
+promise_test(function(test) {
+    return navigator.geofencing.getRegisteredRegions()
+        .then(test.unreached_func('Promise should not have resolved'))
+        .catch(function() {});
+}, 'getRegisteredRegions should fail');