Closed Bug 1836204 Opened 2 years ago Closed 2 years ago

Re-enable browser.translations.enable for automation

Categories

(Firefox :: Translations, defect, P2)

defect

Tracking

()

RESOLVED FIXED
118 Branch
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
Component: Agent → Translation
Product: Remote Protocol → Firefox
Keywords: regression
Regressed by: 1831963

Greg: just a quick ping, in case you want to investigate this issue we filed this bug.

Flags: needinfo?(gtatum)

Set release status flags based on info from the regressing bug 1831963

Thanks, I'll look more into performance work and revisit.

Flags: needinfo?(gtatum)

Set release status flags based on info from the regressing bug 1831963

Blocks: 1820261

Blocking Bug 1820261 because this prevents from checking the performance impact of the translations feature in CI

The severity field is not set for this bug.
:nordzilla, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(enordin)
Type: task → defect
Flags: needinfo?(enordin)

The severity field is not set for this bug.
:nordzilla, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(enordin)

I am just waiting for Bug 1836974 to land before re-attempting this.

Severity: -- → S3
Priority: -- → P2
Assignee: nobody → gtatum
Depends on: 1836974
Flags: needinfo?(enordin)

Greg, should we reenable it now? Thanks

Flags: needinfo?(gtatum)
Flags: needinfo?(gtatum)
Pushed by mcastelluccio@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/790939d4314e Re-enable translations in automation; r=nordzilla,webdriver-reviewers,whimboo
Regressions: 1842222

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

Pushed by gtatum@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/0ab331879e6d Re-enable translations in automation; r=nordzilla,webdriver-reviewers,whimboo https://hg.mozilla.org/integration/autoland/rev/1316e023af44 Fix memory leak with the ViewShown listener; r=nordzilla
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 117 Branch
Flags: needinfo?(gtatum)

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.

Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Target Milestone: 117 Branch → ---
Pushed by ctuns@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/f21e171c96b3 Fix prettier lint failures. r=fix CLOSED TREE
Pushed by archaeopteryx@coole-files.de: https://hg.mozilla.org/integration/autoland/rev/122bcfb45013 Re-enable translations in automation; r=nordzilla,webdriver-reviewers,whimboo https://hg.mozilla.org/integration/autoland/rev/14debb6cb956 Fix memory leak with the ViewShown listener; r=nordzilla CLOSED TREE

This relanded because the backout caused test failures. There was a conflict backing out bug 1845428.

this has caused a regression bug 1805613;

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.

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.

Flags: needinfo?(aryx.bugmail)
Status: REOPENED → RESOLVED
Closed: 2 years ago2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 118 Branch

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.

Flags: needinfo?(aryx.bugmail)
Regressions: 1846806
Flags: needinfo?(gtatum)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: