forked from mirrors/gecko-dev
4ec6b65323
The main reason to do this is to avoid polluting developer's terminals _after_ Firefox exits; regular users shouldn't see `pingsender` logging at all. It's not technically difficult to actually launch with null stdout and stderr, but it is quite onerous: we have at least two ways to launch processes (`LaunchApp` and `nsIProcess`), with platform specific differences and implementation specific options. This approach is at least brief and easy to understand. Differential Revision: https://phabricator.services.mozilla.com/D163153
13 lines
629 B
JavaScript
13 lines
629 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/. */
|
|
|
|
export async function runBackgroundTask(commandLine) {
|
|
// Exact same behaviour as `unique_profile`, but with a task name
|
|
// that is recognized as a task that should produce no output.
|
|
const taskModule = ChromeUtils.import(
|
|
"resource://testing-common/backgroundtasks/BackgroundTask_unique_profile.jsm"
|
|
);
|
|
return taskModule.runBackgroundTask(commandLine);
|
|
}
|