Closed Bug 1714698 Opened 4 years ago Closed 11 months ago

[meta] Fix Fission mochitests for Android

Categories

(GeckoView :: General, task, P2)

Product:
GeckoView
Component:
General
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED FIXED
Milestone:
Future

People

(Reporter: owlish, Unassigned)

References

(Blocks 2 open bugs)

Details

(Keywords: meta, Whiteboard: [fission:android:m2] [geckoview:2022q3] [geckoview:m104] [geckoview:m105] [geckoview:m106] [geckoview:m107] [geckoview:2022q4])

Affected tests:

  • mochitest-plain-fis
  • mochitest-plain-fis-xorig

These have multiple failures across chunks on all six builds we are currently running them on (android-em-7.0-x86_64-qr/debug, android-em-7.0-x86_64-qr/opt, android-em-7.0-x86_64-shippable-qr/opt, android-em-7.0-x86_64-shippable/opt, android-em-7.0-x86_64/debug, android-em-7.0-x86_64/opt)

We currently don't run mochitest-media-fis, but it fails on android-em-7.0-x86_64/debug and android-em-7.0-x86_64-qr/debug. Affected tests:

  • dom/media/autoplay/test/mochitest/test_autoplay_gv_play_request.html
  • dom/media/mediasession/test/test_trigger_actionhanlder.html
  • dom/media/webrtc/tests/mochitests/identity/test_loginNeeded.html
  • dom/media/webrtc/tests/mochitests/identity/test_fingerprints.html
Product: Testing → GeckoView
Target Milestone: --- → Future
Version: Default → Trunk
Fission Milestone: --- → Future
Whiteboard: [fission:android:m2]

Additional info: The result of ./mach try fuzzy —full -q ‘android’ https://treeherder.mozilla.org/jobs?repo=try&revision=f76f23544a54226b64839d44961aca5a51e10f82

Severity: -- → S3
Priority: -- → P3
Fission Milestone: Future → ---
Depends on: 1753772
Depends on: 1754293
Depends on: 1754607

Jon will identify which mochitests are currently failing with Android Fission and file bugs for failing tests.

Assignee: nobody → jonalmeida942
Severity: S3 → N/A
Priority: P3 → P1
Summary: Fix fission mochitests for Android → Fix Fission mochitests for Android
Whiteboard: [fission:android:m2] → [fission:android:m2] [geckoview:m104]

Moving Android Fission bugs to the new GeckoView::Sandboxing component.

Component: General → Sandboxing

105

Whiteboard: [fission:android:m2] [geckoview:m104] → [fission:android:m2] [geckoview:m104] [geckoview:m105]
Whiteboard: [fission:android:m2] [geckoview:m104] [geckoview:m105] → [fission:android:m2] [geckoview:2022q3] [geckoview:m104] [geckoview:m105] [geckoview:m106]

107

Whiteboard: [fission:android:m2] [geckoview:2022q3] [geckoview:m104] [geckoview:m105] [geckoview:m106] → [fission:android:m2] [geckoview:2022q3] [geckoview:m104] [geckoview:m105] [geckoview:m106] [geckoview:m107]

P2

Priority: P1 → P2
Whiteboard: [fission:android:m2] [geckoview:2022q3] [geckoview:m104] [geckoview:m105] [geckoview:m106] [geckoview:m107] → [fission:android:m2] [geckoview:2022q3] [geckoview:m104] [geckoview:m105] [geckoview:m106] [geckoview:m107] [geckoview:2022q4]
Blocks: gv-fission
Depends on: 1822711

I have looked at all the errors and summarized them here.

Turning this bug into a meta.

Assignee: jonalmeida942 → nobody
Priority: P2 → P1
Summary: Fix Fission mochitests for Android → [meta] Fix Fission mochitests for Android
Depends on: 1827313
Depends on: 1827314
Depends on: 1855511

The Android team has not been keeping our P1 bug list up to date, so we're resetting all our P1 bugs to P2 to avoid signalling that we're actively working on bugs that we're not. The BMO documentation https://wiki.mozilla.org/BMO/UserGuide/BugFields#priority says P1 means "fix in the current release cycle" and P2 means "fix in the next release cycle or the following (nightly + 1 or nightly + 2)".

If you are actively working on this bug and expect to ship it in Fx 122 or 123, then please restore the priority back to P1.

Priority: P1 → P2
Depends on: 1777566
Component: Sandboxing → General
Status: NEW → RESOLVED
Closed: 11 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.