Bug 1482091: Follow-up: Whitelist errors in yet another fullscreen test. r=bustage
authorKris Maglione <maglione.k@gmail.com>
Fri, 02 Nov 2018 18:05:14 -0700
changeset 500743 cad4c41bf7fefbc2f2142ce9d57c7b0a0ee8c4a8
parent 500742 dfd04bbbf00d65f7a474ccbf800878f69799e7b6
child 500744 63f135d2db22375b51cf0ded745279afe2188022
push id10290
push userffxbld-merge
push dateMon, 03 Dec 2018 16:23:23 +0000
treeherdermozilla-beta@700bed2445e6 [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersbustage
bugs1482091
milestone65.0a1
first release with
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
Bug 1482091: Follow-up: Whitelist errors in yet another fullscreen test. r=bustage
dom/html/test/browser_fullscreen-contextmenu-esc.js
--- a/dom/html/test/browser_fullscreen-contextmenu-esc.js
+++ b/dom/html/test/browser_fullscreen-contextmenu-esc.js
@@ -1,10 +1,16 @@
 "use strict";
 
+// This test tends to trigger a race in the fullscreen time telemetry,
+// where the fullscreen enter and fullscreen exit events (which use the
+// same histogram ID) overlap. That causes TelemetryStopwatch to log an
+// error.
+SimpleTest.ignoreAllUncaughtExceptions(true);
+
 function frameScript() {
   addMessageListener("Test:RequestFullscreen", () => {
     content.document.body.requestFullscreen();
   });
   content.document.addEventListener("fullscreenchange", () => {
     sendAsyncMessage("Test:FullscreenChanged",
                      !!content.document.fullscreenElement);
   });