File: updateMutexTestChild.js

package info (click to toggle)
firefox 149.0-1
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 4,767,760 kB
  • sloc: cpp: 7,416,064; javascript: 6,752,859; ansic: 3,774,850; python: 1,250,473; xml: 641,578; asm: 439,191; java: 186,617; sh: 56,634; makefile: 18,856; objc: 13,092; perl: 12,763; pascal: 5,960; yacc: 4,583; cs: 3,846; lex: 1,720; ruby: 1,002; php: 436; lisp: 258; awk: 105; sql: 66; sed: 53; csh: 10; exp: 6
file content (35 lines) | stat: -rw-r--r-- 1,173 bytes parent folder | download | duplicates (13)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
/* Any copyright is dedicated to the Public Domain.
 * http://creativecommons.org/publicdomain/zero/1.0/
 */

// This is the script that runs in the child xpcshell process when using
// TestUpdateMutexCrossProcess, like we do in
// unit_aus_update/canCheckForAndCanApplyUpdates.js.
// The main thing this script does is try to acquire update mutex in the same
// fake environment in which the parent runs, which we must set up.
// This requires that our command line defines of the relevant helper functions
// from xpcshellUtilsAUS.js, which are:
/* global registerCustomDirProvider */
/* global resetSyncManagerLock */
/* global EXIT_CODE */

print("child process is running");

registerCustomDirProvider();
resetSyncManagerLock();

var updateMutex = Cc["@mozilla.org/updates/update-mutex;1"].createInstance(
  Ci.nsIUpdateMutex
);
if (!updateMutex.tryLock()) {
  quit(EXIT_CODE.FAILED_TO_ACQUIRE_UPDATE_MUTEX);
}

// Wait for 60 seconds, then exit. We expect that the parent will kill us first.
print(
  "child process should now have the update mutex; will exit in 60 seconds"
);
simulateNoScriptActivity(60);
print("child process exiting now");

updateMutex.unlock();