Closed Bug 1239954 Opened 8 years ago Closed 6 years ago

xpcshell test timed out with SettingsSevice.createlock().get()

Categories

(Firefox OS Graveyard :: General, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: tnguyen, Unassigned)

References

Details

I'm writing some xpcshell test cases running on emulator-kk and found that if the code contains SettingsSevice.createlock().get(), xpcshell test will be timed out, even all the tests are run as PASS.
Trying to run a simple test as below
"use strict";

/* globals run_next_test, add_test, ok, equal, Components, XPCOMUtils */
/* exported run_test */

const {classes: Cc, interfaces: Ci, utils: Cu} = Components;


Cu.import("resource://gre/modules/XPCOMUtils.jsm");
XPCOMUtils.defineLazyServiceGetter(this, "gSettingsService",
                                   "@mozilla.org/settingsService;1",
                                   "nsISettingsService");
let lock = gSettingsService.createLock();
lock.get("nfc.debugging.enbled", null);


function run_test() {

  run_next_test();
}

add_test(function test_setFocusTab() {
    run_next_test();
});

Then the test will be easily failed as timed out error
Blocks: 907252
Does this happen on emulator-x86-kk w/wo kvm enabled?
I have not tried, let me create emulator-x86-kk environment and try
I tried with emulator-x86-kk and the same issue.
I got 1 time OK, but actually due to crash 

3:23.10 LOG: MainThread INFO Running tests sequentially.
 3:23.10 SUITE_START: MainThread 1
 3:23.57 LOG: Thread-1 INFO profile dir is /data/local/tests/xpc/p
 3:24.52 TEST_START: Thread-1 dom/nfc/tests/unit/test_Nfc.js
 3:34.45 TEST_END: Thread-1 PASS
PROCESS-CRASH | dom/nfc/tests/unit/test_Nfc.js | application crashed [unknown top frame]
Crash dump filename: /tmp/tmpFfw8tB/1731da82-3f44-893e-2e27c2b5-772a3b24.dmp
MINIDUMP_STACKWALK not set, can't process dump.
 3:36.52 LOG: MainThread INFO INFO | Result summary:
 3:36.52 LOG: MainThread INFO INFO | Passed: 1
 3:36.52 LOG: MainThread INFO INFO | Failed: 1
 3:36.52 LOG: MainThread INFO INFO | Todo: 0
 3:36.52 LOG: MainThread INFO INFO | Retried: 0
 3:36.52 SUITE_END: MainThread 
Summary
=======

Ran 1 tests
Expected results: 1
Unexpected results: 0

OK
Automation Error: Exception caught while running tests
Traceback (most recent call last):
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.