Closed
Bug 885389
Opened 12 years ago
Closed 10 years ago
xpcshell head.js doesn't notify profile-after-change
Categories
(Testing :: XPCShell Harness, defect)
Testing
XPCShell Harness
Tracking
(firefox40 fixed)
RESOLVED
FIXED
mozilla40
Tracking | Status | |
---|---|---|
firefox40 | --- | fixed |
People
(Reporter: rnewman, Assigned: gfritzsche)
References
Details
Attachments
(2 files, 1 obsolete file)
1.88 KB,
patch
|
ted
:
review+
|
Details | Diff | Splinter Review |
4.69 KB,
patch
|
ted
:
review+
|
Details | Diff | Splinter Review |
It only sends profile-do-change.
I found this while trying to figure out why FormHistory wasn't uniniting itself (Bug 878677).
Is there a reason why it doesn't?
Adding a call to do so doesn't seem to break anything:
15:31.89 INFO | Result summary:
15:31.89 INFO | Passed: 1643
15:31.89 INFO | Failed: 2
15:31.89 INFO | Todo: 3
Only the usual kinds of failures:
15:05.50 TEST-UNEXPECTED-FAIL | /Users/rnewman/moz/hg/services-central/obj-ff-dbg/_tests/xpcshell/toolkit/mozapps/update/test/unit/test_0201_app_launch_apply_update.js | test failed (with xpcshell return code: 3), see following log:
15:05.50 >>>>>>>
15:05.50 ### XPCOM_MEM_LEAK_LOG defined -- logging leaks to /var/folders/2b/fnxwv4mj1bqc8qbkhdzc13s80000gn/T/tmp3Jabbx/runxpcshelltests_leaks.log
15:05.50
15:05.50 TEST-INFO | (xpcshell/head.js) | test MAIN run_test pending (1)
15:05.50
15:05.50 TEST-INFO | (xpcshell/head.js) | test pending (2)
15:05.50
15:05.50 TEST-UNEXPECTED-FAIL | /Users/rnewman/moz/hg/services-central/obj-ff-dbg/_tests/xpcshell/toolkit/mozapps/update/test/unit/head_update.js:3059 | ReferenceError: BUNDLE_NAME is not defined - See following stack:
15:05.50 JS frame :: getAppDir@/Users/rnewman/moz/hg/services-central/obj-ff-dbg/_tests/xpcshell/toolkit/mozapps/update/test/unit/head_update.js:3059
15:05.50 JS frame :: symlinkUpdateFilesIntoBundleDirectory@/Users/rnewman/moz/hg/services-central/obj-ff-dbg/_tests/xpcshell/toolkit/mozapps/update/test/unit/test_0201_app_launch_apply_update.js:59
15:05.50 JS frame :: run_test@/Users/rnewman/moz/hg/services-central/obj-ff-dbg/_tests/xpcshell/toolkit/mozapps/update/test/unit/test_0201_app_launch_apply_update.js:118
15:05.50 JS frame :: _execute_test@/Users/rnewman/moz/hg/services-central/testing/xpcshell/head.js:325
15:05.50 JS frame :: @-e:1
15:05.50 /Users/rnewman/moz/hg/services-central/obj-ff-dbg/_tests/xpcshell/toolkit/mozapps/update/test/unit/test_0201_app_launch_apply_update.js:212: TypeError: gProcess is undefined
4:01.72 TEST-UNEXPECTED-FAIL | /Users/rnewman/moz/hg/services-central/obj-ff-dbg/_tests/xpcshell/netwerk/test/unit/test_protocolproxyservice.js | "127.0.0.1" != "127.0.0.1" - See following stack:
4:01.72 JS frame :: /Users/rnewman/moz/hg/services-central/obj-ff-dbg/_tests/xpcshell/netwerk/test/unit/test_protocolproxyservice.js :: myipaddress_callback :: line 598
4:01.72 JS frame :: /Users/rnewman/moz/hg/services-central/obj-ff-dbg/_tests/xpcshell/netwerk/test/unit/test_protocolproxyservice.js :: resolveCallback.prototype.onProxyAvailable :: line 152
Attachment #765424 -
Flags: review?(dteller)
Reporter | ||
Comment 1•12 years ago
|
||
Per mak:
This is for the simple reason there are various components that are inited by profile-after-change and it would be crazy to always invoke it and load a bunch of useless components. profile-after-change must indeed be notified manually.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
Comment 2•12 years ago
|
||
Comment on attachment 765424 [details] [diff] [review]
Incorrectly absolute patch.
That being said, I think it would be fine to add a parameter to do_get_profile to send this notification instead of making tests send it manually.
Reporter | ||
Updated•12 years ago
|
Attachment #765424 -
Attachment description: Proposed patch. v1 → Incorrectly absolute patch.
Attachment #765424 -
Flags: review?(dteller)
Reporter | ||
Comment 3•12 years ago
|
||
Then let's keep this one open.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Reporter | ||
Updated•12 years ago
|
Status: REOPENED → NEW
Comment 4•12 years ago
|
||
(In reply to Ted Mielczarek [:ted.mielczarek] from comment #2)
> Comment on attachment 765424 [details] [diff] [review]
> Incorrectly absolute patch.
>
> That being said, I think it would be fine to add a parameter to
> do_get_profile to send this notification instead of making tests send it
> manually.
Possibly, though it will still initialize a lot of components that the test doesn't need, and that may be an issue for 2 reasons:
1. unexpected failures due to not setting up the env for those components properly (after all it's not the component you are testing)
2. slower test runs, with increased use of resources
My idea of "sending it manually" is not through a global notifyObservers() call, but by directly invoking .observe() of the component manually, so that only that specific component is initialized, that is what we did so far.
Reporter | ||
Updated•12 years ago
|
Assignee: rnewman → nobody
Assignee | ||
Comment 5•11 years ago
|
||
Assignee: nobody → gfritzsche
Attachment #765424 -
Attachment is obsolete: true
Status: NEW → ASSIGNED
Attachment #8589144 -
Flags: review?(ted)
Updated•10 years ago
|
Attachment #8589144 -
Flags: review?(ted) → review+
Comment 6•10 years ago
|
||
This could also probably stand a test in testing/xpcshell/example.
Assignee | ||
Comment 7•10 years ago
|
||
Assignee | ||
Updated•10 years ago
|
Attachment #8595312 -
Flags: review?(ted)
Comment 8•10 years ago
|
||
Comment on attachment 8595312 [details] [diff] [review]
Add test coverage for do_get_profile() observer notifications
Review of attachment 8595312 [details] [diff] [review]:
-----------------------------------------------------------------
Very thorough, nice!
Attachment #8595312 -
Flags: review?(ted) → review+
https://hg.mozilla.org/mozilla-central/rev/025e4c11ed7e
https://hg.mozilla.org/mozilla-central/rev/d0e1fb64877c
Status: ASSIGNED → RESOLVED
Closed: 12 years ago → 10 years ago
status-firefox40:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla40
You need to log in
before you can comment on or make changes to this bug.
Description
•