Bug 1381799 - Fix intermittent test_alarm_clear_non_matching_name r=aswan

The failure from the bug could happen if the test runs so slow that the
timer expires before the existence of the alarm is checked.
To avoid that failure, extend the lifetime of the alarm from 2 to 2000
seconds.

Differential Revision: https://phabricator.services.mozilla.com/D4678

--HG--
extra : moz-landing-system : lando
This commit is contained in:
Rob Wu 2018-08-30 15:33:12 +00:00
parent 7602f12fd8
commit 404b079aa8

View File

@ -105,7 +105,7 @@ add_task(async function test_alarm_clear_non_matching_name() {
async function backgroundScript() {
let ALARM_NAME = "test_ext_alarms";
browser.alarms.create(ALARM_NAME, {when: Date.now() + 2000});
browser.alarms.create(ALARM_NAME, {when: Date.now() + 2000000});
let wasCleared = await browser.alarms.clear(ALARM_NAME + "1");
browser.test.assertFalse(wasCleared, "alarm was not cleared");
@ -129,7 +129,7 @@ add_task(async function test_alarm_clear_non_matching_name() {
add_task(async function test_alarm_get_and_clear_single_argument() {
async function backgroundScript() {
browser.alarms.create({when: Date.now() + 2000});
browser.alarms.create({when: Date.now() + 2000000});
let alarm = await browser.alarms.get();
browser.test.assertEq("", alarm.name, "expected alarm returned");