forked from mirrors/gecko-dev
b29166e40c
There are some complications here to handle unpackaged and packaged builds. In addition, there could be a difference between App prefs and GRE prefs. Since the underlying backgroundtasks code is built as part of Gecko (i.e., `toolkit/...` rather than `browser/...`) I have favoured GRE prefs. I think, however, that what is written will work for App-specific prefs, but I'm not concerned with that detail at this time. This also add tests for backgroundtask-specific prefs, which are structured as both xpcshell and mochitest-chrome tests because locally, the former tests unpackaged builds and the latter can accommodate testing packaged builds. We could use mochitest-chrome for both, but this has been pleasant to work with locally. Differential Revision: https://phabricator.services.mozilla.com/D97510
23 lines
815 B
JavaScript
23 lines
815 B
JavaScript
/* -*- indent-tabs-mode: nil; js-indent-level: 2 -*-
|
|
* This Source Code Form is subject to the terms of the Mozilla Public
|
|
* License, v. 2.0. If a copy of the MPL was not distributed with this
|
|
* file, You can obtain one at http://mozilla.org/MPL/2.0/. */
|
|
|
|
var EXPORTED_SYMBOLS = ["runBackgroundTask"];
|
|
|
|
const { Services } = ChromeUtils.import("resource://gre/modules/Services.jsm");
|
|
|
|
async function runBackgroundTask(commandLine) {
|
|
let pref = commandLine.length
|
|
? commandLine.getArgument(0)
|
|
: "test.backgroundtask_specific_pref.exitCode";
|
|
|
|
// 0, 1, 2, 3 are all meaningful exit codes already.
|
|
let exitCode = Services.prefs.getIntPref(pref, 4);
|
|
|
|
console.error(
|
|
`runBackgroundTask: backgroundtask_specific_pref read pref '${pref}', exiting with exitCode ${exitCode}`
|
|
);
|
|
|
|
return exitCode;
|
|
}
|