Update unit tests to replace headerURL, accentcolor, textcolor
Categories
(WebExtensions :: Themes, task, P1)
Tracking
(firefox71 fixed)
Tracking | Status | |
---|---|---|
firefox71 | --- | fixed |
People
(Reporter: robwu, Assigned: robwu)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
There are a bunch of tests in toolkit/mozapps/extensions/test/xpcshell/ that use the removed headerURL
:
https://searchfox.org/mozilla-central/search?q=headerURL&case=false®exp=false&path=test%2Fxpcshell
The tests themselves just need a theme and don't really care about the effect of the theme, so the absence of headerURL
didn't cause the test to fail. I do however see deprecation messages in the console.
It's easy enough to fix those (simply replace headerURL
with theme_frame
).
I wonder whether we should introduce a (default-on in unit tests) pref to treat deprecation warnings in extensions as errors, to make sure that such issues never happen again.
Assignee | ||
Comment 1•5 years ago
|
||
Assignee | ||
Comment 2•5 years ago
|
||
Add new preference extensions.webextensions.warnings-as-errors
that
defaults to true
in tests. Tests that expect warnings are modified
to briefly flip the pref for the specific part of the test that needs
an exception.
Assignee | ||
Updated•5 years ago
|
Updated•5 years ago
|
Comment 4•5 years ago
•
|
||
Rob, could you please take a look into these speedometer max run time outs? https://treeherder.mozilla.org/#/jobs?repo=autoland&group_state=expanded&searchStr=android%2C7.0%2Cmotog5%2Cpgo%2Craptor%2Cperformance%2Ctests%2Con%2Cfirefox%2Ctest-android-hw-g5-7-0-arm7-api-16%2Fpgo-raptor-speedometer-geckoview-e10s%2Crap%28sp%29&tochange=013bdea4e8e3020016b428e90ac967a08e123bdb&fromchange=4e6dd979ed238a6c0be55ecfb8a42d6ca417d865&selectedJob=266601867
Filed bug 1581223 to track those failures.
Assignee | ||
Comment 5•5 years ago
|
||
I'll take a look. Most likely the raptor extension is using a deprecated API.
Comment 6•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/51824b1dda97
https://hg.mozilla.org/mozilla-central/rev/e7364a10a663
Comment 7•5 years ago
|
||
Backed out for causing tp6m raptor failures (Bug 1568050)
Backout link: https://hg.mozilla.org/integration/autoland/rev/72d9ad70e1ba7d56e9e3732cfd912f53c348a9a8
Log link: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=266548810&repo=autoland&lineNumber=1499
Assignee | ||
Comment 8•5 years ago
|
||
This was going to be fixed by bug 1581223 .
The patch can reland without changes, together with bug 1581223
Comment 9•5 years ago
|
||
Backout merged: https://hg.mozilla.org/mozilla-central/rev/72d9ad70e1ba
Comment 10•5 years ago
|
||
Comment 11•5 years ago
|
||
The android-hw devices have been using a new image with a newer python2. This started on 9/11 12PM pacific to 9/12 12PM and then has continued from 9/13 5PM pacific onward. The newer python2 may be unoptimized compared to the default py2 on ubuntu. :bobclary questioned if python performance could affect the timing of on-device operations. Let me know if the bisect doesn't reveal anything.
Assignee | ||
Comment 12•5 years ago
|
||
@Andrew I suggest to (re)post that comment at bug 1568050.
Comment 13•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/1124b75d02a6
https://hg.mozilla.org/mozilla-central/rev/dc3646b4f5a2
Comment 14•5 years ago
|
||
Hello,
Will this fix require manual validation? If yes, please provide some steps to reproduce in order to correctly test it and also, please set the "qe-verify+" flag. Otherwise, could the "qe-verify-" flag be added? Thanks!
Assignee | ||
Updated•5 years ago
|
Description
•