Move addons-search-detection in tree
Categories
(WebExtensions :: General, task, P3)
Tracking
(firefox95 verified)
Tracking | Status | |
---|---|---|
firefox95 | --- | verified |
People
(Reporter: willdurand, Assigned: willdurand)
References
Details
(Whiteboard: [addons-jira])
Attachments
(1 file)
We'd like to move the addons-search-detection system add-on in tree (in this folder) to be able to: (1) write some tests, (2) avoid the signing/Balrog processes in the future.
We don't have much plans to integrate some of the features of the add-on in a better place yet so there is value in simply transferring most of the existing code into browsers/extensions/
and write tests (in a different bug probably).
:mixedpuppy said it was OK to do it because the code of the extension on GitHub has been reviewed by both :mixedpuppy and :robwu already. Some additional build-related files/configs will be needed but that should be it.
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Assignee | ||
Comment 1•3 years ago
|
||
Note: we should create a built-in add-on.
Assignee | ||
Comment 2•3 years ago
|
||
This patch moves the addons-search-detection system add-on in tree and
adjusts the build configuration to make it a built-in add-on (which
requires changes in the BrowserGlue.jsm
file).
Updated•3 years ago
|
Assignee | ||
Updated•3 years ago
|
Comment 4•3 years ago
|
||
Backed out for causing failures at browser_all_files_referenced.js.
Backout link: https://hg.mozilla.org/integration/autoland/rev/47cd6e2ed3184ec2001ea1255c03bd45c7fb7d18
Failure log: https://treeherder.mozilla.org/logviewer?job_id=355367382&repo=autoland&lineNumber=3562
Assignee | ||
Comment 5•3 years ago
|
||
Looks like the test case does not support all the files we bundle for this add-on. I talked to :rpl and he told me to fix the test case as opposed to exclude the built-in add-on in this test case so I am going to do that now.
Comment 7•3 years ago
|
||
Backed out for causing mochitests browser chrome failures on browser_startup_syncIPC.js.
Updated•3 years ago
|
Assignee | ||
Comment 8•3 years ago
|
||
I updated the patch to fix the issue in browser_startup_syncIPC.js
. Not sure exactly why this happened right now but :florian agreed to add an exception in the test file for this add-on.
Comment 10•3 years ago
|
||
bugherder |
Comment 11•3 years ago
|
||
Verified the patch on the latest Nightly 95 (95.0a1/20211021215643) under Windows 10 x64 and Ubuntu 16.04 LTS.
The “Add-ons Search Detection” add-on is now built-in Firefox. It’s listed in about:support under “Add-ons” with version 2.0.0, confirming the patch.
Comment 12•3 years ago
|
||
Hello. This bug or Bug 1736825 has caused this regression. Can you please help with identifying which one might be the cause?
Assignee | ||
Updated•3 years ago
|
Comment 13•3 years ago
|
||
Hi,
Could you please tell me if it makes sense for these improvements to be caused by this patch?
== Change summary for alert #32142 (as of Wed, 27 Oct 2021 14:41:10 GMT) ==
Improvements:
Ratio | Test | Platform | Options | Absolute values (old vs new) |
---|---|---|---|---|
6% | build times | windows2012-32-shippable | nightly taskcluster-m5d.4xlarge | 1,951.29 -> 1,840.96 |
4% | build times | windows2012-64-shippable | nightly taskcluster-m5.4xlarge | 1,996.99 -> 1,923.03 |
4% | build times | osx-shippable | nightly taskcluster-c5n.4xlarge | 2,617.88 -> 2,524.89 |
For up to date results, see: https://treeherder.mozilla.org/perfherder/alerts?id=32142
Here is a link with all the alerts in the same graph
https://treeherder.mozilla.org/perfherder/graphs?highlightAlerts=1&highlightChangelogData=1&series=autoland,2741922,1,2&series=autoland,2310089,1,2&series=autoland,2734448,1,2&timerange=2592000&zoom=1634606732479,1634860649898,1587.2015054889448,2882.455655980151
Comment 14•3 years ago
|
||
This added more to the build, so I don't think that this would cause an improvement.
Assignee | ||
Updated•3 years ago
|
Comment 15•3 years ago
•
|
||
(In reply to Shane Caraveo (:mixedpuppy) from comment #14)
This added more to the build, so I don't think that this would cause an improvement.
This appears to be the pushlog for the improvement range: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=fefc5982e76658e6d6dd49308c51dd8933542153&tochange=8de0d1e269d09e73d54b04213adce6ee0e5988ab.
Is there another revision that looks more likely to be the cause?
Comment 16•3 years ago
|
||
I would say the patch to upgrade the build system to clang-13 looks like the best candidate to affect build times:
https://hg.mozilla.org/integration/autoland/rev/dcb91b95f32bb7692169357bc6c8d1cfa81e34c1
Comment 17•3 years ago
|
||
(In reply to Tomislav Jovanovic :zombie from comment #16)
I would say the patch to upgrade the build system to clang-13 looks like the best candidate to affect build times:
https://hg.mozilla.org/integration/autoland/rev/dcb91b95f32bb7692169357bc6c8d1cfa81e34c1
Agreed, thanks!
Description
•