Closed
Bug 1309961
Opened 9 years ago
Closed 9 years ago
TEST-UNEXPECTED-FAIL | toolkit/mozapps/update/tests/unit_aus_update/updateManagerXML.js
Categories
(Toolkit :: Application Update, defect)
Toolkit
Application Update
Tracking
()
RESOLVED
FIXED
mozilla52
Tracking | Status | |
---|---|---|
firefox49 | --- | unaffected |
firefox-esr45 | --- | unaffected |
firefox50 | --- | fixed |
firefox51 | --- | fixed |
firefox52 | --- | fixed |
People
(Reporter: jorgk-bmo, Assigned: robert.strong.bugs)
References
Details
(Keywords: intermittent-failure)
Attachments
(1 file, 1 obsolete file)
2.37 KB,
patch
|
molly
:
review+
|
Details | Diff | Splinter Review |
First seen Thu Oct 13, 2016 here
https://treeherder.mozilla.org/#/jobs?repo=comm-central&revision=593964199b659fdb8b5b7d8ce765c1976a783c99&selectedJob=49911
(not the initial push but the Nightly run on the same push).
TEST-UNEXPECTED-FAIL | toolkit/mozapps/update/tests/unit_aus_update/updateManagerXML.js | xpcshell return code: 0
TEST-UNEXPECTED-FAIL | toolkit/mozapps/update/tests/unit_aus_update/updateManagerXML.js | run_test - [run_test : 145] the update backgroundInterval attribute should equal the expected value - 60 == "600"
Comment 1•9 years ago
|
||
The bug won't show up on treeherder without this keyword.
Keywords: intermittent-failure
Reporter | ||
Comment 2•9 years ago
|
||
Looks like this comes from
https://hg.mozilla.org/mozilla-central/rev/3f592df38fe2
https://hg.mozilla.org/mozilla-central/rev/9837e6ec214e
from bug 1309125.
Seems to be caused by app.update.download.backgroundInterval which is set to 60:
https://dxr.mozilla.org/comm-central/search?q=app.update.download.backgroundInterval
Re. comment #1. Sorry, I keep forgetting. Besides, we want to fix this quickly, right? Aleth, can you take a look? What am I missing. Where does the 600 come from?
Comment 3•9 years ago
|
||
How is backgroundInterval being set to 600? The corresponding prefs seem to be set to 60. Is there a value in the update.xml now?
Updated•9 years ago
|
Flags: needinfo?(robert.strong.bugs)
![]() |
Assignee | |
Comment 4•9 years ago
|
||
It appears that somehow that Thunderbird pref is being loaded in the xpcshell test for Thunderbird which I don't think it should be since it is an xpcshell test and the same pref is not loaded when running the xpcshell tests with a Firefox build.
Flags: needinfo?(robert.strong.bugs)
![]() |
Assignee | |
Comment 5•9 years ago
|
||
aleth, could you check if the patch fixes this for Thunderbird?
Flags: needinfo?(aleth)
Comment 6•9 years ago
|
||
Unfortunately, it does not seem to have any effect.
https://treeherder.mozilla.org/#/jobs?repo=try-comm-central&revision=ddbac06ad33db8146187641d5a053da58a83d4e9
Flags: needinfo?(aleth) → needinfo?(robert.strong.bugs)
![]() |
Assignee | |
Comment 7•9 years ago
|
||
I'm building thunderbird to see if I can reproduce.
Flags: needinfo?(robert.strong.bugs)
Reporter | ||
Comment 8•9 years ago
|
||
That's very kind of you. I was going to do the same since my build predates the landing of the original bug. Sadly it takes about 70 minutes to build which I couldn't squeeze in today.
Reporter | ||
Comment 9•9 years ago
|
||
You go:
./mozilla/mach xpcshell-test toolkit/mozapps/update/tests/unit_aus_update/updateManagerXML.js
There's no mozilla in front of toolkit/
Just is case you didn't know (since I've met M-C people who didn't know). It's always hard to tell who is a friend of TB and who is a foe ;-)
![]() |
Assignee | |
Comment 10•9 years ago
|
||
No worries and I've been a friend for over 10 years. :)
I even already have a c-c repo locally and build periodically.
![]() |
Assignee | |
Comment 11•9 years ago
|
||
heh... for some reason I thought the failing test was remoteUpdateXML.js and not updateManagerXML.js. The change in the attached patch when made to updateManagerXML.js does fix this bug. I'll take this.
Component: General → Application Update
Product: Thunderbird → Toolkit
![]() |
Assignee | |
Updated•9 years ago
|
Assignee: nobody → robert.strong.bugs
Status: NEW → ASSIGNED
![]() |
Assignee | |
Comment 12•9 years ago
|
||
BTW: it does appear that thunderbird prefs are being applied to xpcshell tests whereas firefox prefs are not. Just a heads up and I'm not going to research as to why.
![]() |
Assignee | |
Comment 13•9 years ago
|
||
Since these tests expect that preference to not be set I am removing it in both tests just in case.
Attachment #8800914 -
Attachment is obsolete: true
Attachment #8801333 -
Flags: review?(mhowell)
Updated•9 years ago
|
Attachment #8801333 -
Flags: review?(mhowell) → review+
Comment 14•9 years ago
|
||
Pushed by rstrong@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/238cebc6be2e
don't allow preferences to interfere with running updateManagerXML.js test. r=mhowell
![]() |
||
Comment 15•9 years ago
|
||
You can see where this pref is set in TB:
https://dxr.mozilla.org/comm-central/search?q=app.update.download.backgroundInterval&redirect=false
There is a place that sets it to 600...
Comment 16•9 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
status-firefox52:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla52
![]() |
Assignee | |
Comment 17•9 years ago
|
||
(In reply to :aceman from comment #15)
> You can see where this pref is set in TB:
> https://dxr.mozilla.org/comm-central/search?q=app.update.download.
> backgroundInterval&redirect=false
>
> There is a place that sets it to 600...
See comment #4
![]() |
Assignee | |
Comment 18•9 years ago
|
||
This test fix was landed in bug 1309125 on mozilla-aurora and mozilla-beta
status-firefox49:
--- → unaffected
status-firefox50:
--- → fixed
status-firefox51:
--- → fixed
status-firefox-esr45:
--- → unaffected
You need to log in
before you can comment on or make changes to this bug.
Description
•