Re-enable browser.translations.enable for automation
Categories
(Firefox :: Translations, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox-esr115 | --- | disabled |
firefox113 | --- | unaffected |
firefox114 | --- | unaffected |
firefox115 | --- | disabled |
firefox116 | --- | disabled |
firefox117 | --- | fixed |
firefox118 | --- | fixed |
People
(Reporter: jdescottes, Assigned: gregtatum)
References
(Regression)
Details
(Keywords: regression)
Attachments
(2 files)
In bug 1836093 we disabled translations for automation (webdriver, CDP, ...) because this was triggering timeouts on early beta (https://bugzilla.mozilla.org/show_bug.cgi?id=1835822).
We should investigate the reason for those timeouts. The tests did not seem to hang in a specific spot but just became slower overall and long tests which would take less than 20s now take more than 80s and reach the timeout.
Two important things to note:
- disabling the preference after starting the browser did not help, we had to disable it before the browser starts to avoid the timeouts
- nightly was not affected by the timeouts, despite having the preference as well
Reporter | ||
Updated•2 years ago
|
Reporter | ||
Updated•2 years ago
|
Reporter | ||
Comment 1•2 years ago
|
||
Greg: just a quick ping, in case you want to investigate this issue we filed this bug.
Comment 2•2 years ago
|
||
Set release status flags based on info from the regressing bug 1831963
Assignee | ||
Comment 3•2 years ago
|
||
Thanks, I'll look more into performance work and revisit.
Comment 4•2 years ago
|
||
Set release status flags based on info from the regressing bug 1831963
Reporter | ||
Comment 5•2 years ago
|
||
Blocking Bug 1820261 because this prevents from checking the performance impact of the translations feature in CI
Updated•2 years ago
|
Comment 6•2 years ago
|
||
The severity field is not set for this bug.
:nordzilla, could you have a look please?
For more information, please visit BugBot documentation.
Updated•2 years ago
|
Comment 7•2 years ago
|
||
The severity field is not set for this bug.
:nordzilla, could you have a look please?
For more information, please visit BugBot documentation.
Assignee | ||
Comment 8•2 years ago
|
||
I am just waiting for Bug 1836974 to land before re-attempting this.
Assignee | ||
Updated•2 years ago
|
Updated•2 years ago
|
Assignee | ||
Comment 10•2 years ago
|
||
Assignee | ||
Updated•2 years ago
|
Comment 11•2 years ago
|
||
Comment 12•2 years ago
|
||
The upstream puppeteer PR is: https://github.com/puppeteer/puppeteer/pull/10522
Comment 13•2 years ago
|
||
Backed out changeset 790939d4314e (Bug 1836204) for causing wd leak failures
Log: https://treeherder.mozilla.org/logviewer?job_id=421902018&repo=autoland
Backout: https://hg.mozilla.org/integration/autoland/rev/67087abbf476604d7a738021132b56b6446bb6ca
Updated•2 years ago
|
Updated•2 years ago
|
Assignee | ||
Comment 14•2 years ago
|
||
This was racing with the popup being shown and the browser window being
closed. If it lost this race, then it would cause a leak.
Depends on D182926
Comment 15•2 years ago
|
||
Comment 16•2 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/0ab331879e6d
https://hg.mozilla.org/mozilla-central/rev/1316e023af44
Assignee | ||
Updated•2 years ago
|
Comment 17•2 years ago
|
||
Backed out from autoland (Gecko 118) for causing frequent marionette / bidi failures:
https://hg.mozilla.org/integration/autoland/rev/5274e9eec10fd09a512295f81cf0a9aec373b119
The Try push in bug 1845518 indicates the issue would persist with that patch.
Updated•2 years ago
|
Comment 18•2 years ago
|
||
Comment 19•2 years ago
|
||
Comment 20•2 years ago
|
||
This relanded because the backout caused test failures. There was a conflict backing out bug 1845428.
Comment 21•2 years ago
|
||
this has caused a regression bug 1805613;
Comment 22•2 years ago
|
||
another note here related to the WDSPEC failures- this only fails on fission (linux + windows); the no-fission (linux + android) seems ok. Also the osx tests seem ok.
Comment 23•2 years ago
•
|
||
Sebastian, can you clarify what you meant here?
Does this mean that you tried to back out Bug 1845428?
I'm extremely confused and quite concerned about the test failures that you linked, e.g.:
There should be 1 telemetry events of type OpenPanel - Got 38, expected 1
...
There should be 2 telemetry events of type OpenPanel - Got 77, expected 2
I have no idea what would be causing over-reporting to Telemetry in this way, and I don't know if it's coming from Glean somehow or from the code itself.
I haven't observed that locally, and those tests were all passing on both locally and on the try servers when that patch landed.
Comment 24•2 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/f21e171c96b3
https://hg.mozilla.org/mozilla-central/rev/122bcfb45013
https://hg.mozilla.org/mozilla-central/rev/14debb6cb956
Comment 25•2 years ago
|
||
I did not try to back out bug 1845428 but there was a conflict for the backout of https://hg.mozilla.org/integration/autoland/rev/14debb6cb956 which got resolved as https://hg.mozilla.org/integration/autoland/rev/5274e9eec10fd09a512295f81cf0a9aec373b119#l1.1 but caused the test failure (please let me know if the conflict got resolved incorrect). Because of the failure, this bug (bug 1836204) got relanded.
Assignee | ||
Updated•2 years ago
|
Description
•