Bug 1325530 - requestLongerTimeout for browser_shown.js; r=mconley
authorGeoff Brown <gbrown@mozilla.com>
Wed, 26 Jul 2017 09:16:18 -0600
changeset 422417 d0a02adc86898fd6e4e9c08728fd303077620265
parent 422416 dac259c934e50ef03405d93eb329c37fd7c32819
child 422418 67a4ed32996b2d4fa3366715212e29f4f9a7c337
push id1517
push userjlorenzo@mozilla.com
push dateThu, 14 Sep 2017 16:50:54 +0000
treeherdermozilla-release@3b41fd564418 [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersmconley
bugs1325530
milestone56.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 1325530 - requestLongerTimeout for browser_shown.js; r=mconley A simple solution to current timeouts. Several other tabcrashed tests already use requestLongerTimeout -- it seems like these tests often have a long run time.
browser/base/content/test/tabcrashed/browser_shown.js
--- a/browser/base/content/test/tabcrashed/browser_shown.js
+++ b/browser/base/content/test/tabcrashed/browser_shown.js
@@ -1,14 +1,17 @@
 "use strict";
 
 const PAGE = "data:text/html,<html><body>A%20regular,%20everyday,%20normal%20page.";
 const COMMENTS = "Here's my test comment!";
 const EMAIL = "foo@privacy.com";
 
+// Avoid timeouts, as in bug 1325530
+requestLongerTimeout(2);
+
 add_task(async function setup() {
   await setupLocalCrashReportServer();
 });
 
 /**
  * This function returns a Promise that resolves once the following
  * actions have taken place:
  *