1840019 - Intermittent Android fis /webdriver/tests/bidi/input/release_actions/sequence.py | test_release_mouse_sequence_resets_dblclick_state[without release actions] - AssertionError: assert [{'button': 0, 'type': 'mousedown'},\n {'button': 0, 'type': 'mouse'

Status: RESOLVED FIXED

(Remote Protocol :: WebDriver BiDi, defect, P5)

Description

[Treeherder Bug Filer]

Filed by: hskupin [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=420342453&repo=try
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/C84ihwPHSAOp1WzQ-ELr5Q/runs/0/artifacts/public/logs/live_backing.log

---

Comment 1

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Note that this is a nofis failure only. With fission enabled the failure is not visible. Not sure if we should spend time on this particular bug given that Fission will be default on Android hopefully soon. Also I cannot reproduce the failure locally on desktop with Fission disabled, so it's a Android only failure.

Comment 2

[Intermittent Failures Robot]

2 failures in 3880 pushes (0.001 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:

• try: 2

Platform and build breakdown:

• android-em-7-0-x86_64-qr: 2
  • opt: 2

For more details, see:
https://treeherder.mozilla.org/intermittent-failures/bugdetails?bug=1840019&startday=2023-06-19&endday=2023-06-25&tree=all

Comment 3

[Intermittent Failures Robot]

1 failures in 3341 pushes (0.0 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:

• try: 1

Platform and build breakdown:

• linux1804-64-tsan-qr: 1
  • opt: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures/bugdetails?bug=1840019&startday=2023-08-07&endday=2023-08-13&tree=all

Comment 4

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Surprisingly with my patch on bug 1848799 this is a perma unexpected pass for at least non-fission builds:
https://treeherder.mozilla.org/jobs?repo=try&revision=2c3078ff58adde385ef6c91a7328edadf6eadedc&searchStr=android

Maybe the metadata changes from the last wpt downstream sync weren't that appropriate and it should still be fission only.

Comment 5

[Henrik Skupin [:whimboo][⌚️UTC+2]]

(In reply to Henrik Skupin [:whimboo][⌚️UTC+2] from comment #4)

Surprisingly with my patch on bug 1848799 this is a perma unexpected pass for at least non-fission builds:
https://treeherder.mozilla.org/jobs?repo=try&revision=2c3078ff58adde385ef6c91a7328edadf6eadedc&searchStr=android

Maybe the metadata changes from the last wpt downstream sync weren't that appropriate and it should still be fission only.

Actually that is the case. The wd2 test jobs as run by the above try build used Fission and as such the tests are actually expected to fail. So the change by the wpt-sync should have caused it to fail.

Comment 6

[Henrik Skupin [:whimboo][⌚️UTC+2]]

As noticed I was using mach try fuzzy --full and Android jobs were run with Fission enabled. The failure only occurred in that mode but not with fission disabled. It might be good to have a follow-up meta data update that marks failing tests as FAIL. Also the original failure was for Fission and as such we have to rename the bug's summary.

Comment 7

[Intermittent Failures Robot]

1 failures in 2218 pushes (0.0 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:

• mozilla-central: 1

Platform and build breakdown:

• linux1804-64-tsan-qr: 1
  • opt: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures/bugdetails?bug=1840019&startday=2023-08-21&endday=2023-08-27&tree=all

Comment 8

[Henrik Skupin [:whimboo][⌚️UTC+2]]

This was actually fixed by bug 1864614.

Comment 9

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Actually lets mark as fixed by bug 1864614.