Open Bug 1600736 Opened 3 years ago Updated 2 years ago

ubuntu1804 - /dom/events/Event-dispatch-redispatch.html | Redispatching mouseup event whose default action dispatches a click event - assert_true: mouseup and click events should've been fired expected true got false

Categories

(Core :: DOM: Core & HTML, defect, P5)

defect

Tracking

()

People

(Reporter: intermittent-bug-filer, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

Attachments

(1 file)

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


[task 2019-12-02T17:50:43.925Z] 17:50:43 INFO - TEST-START | /dom/events/Event-dispatch-redispatch.html
[task 2019-12-02T17:50:43.929Z] 17:50:43 INFO - Closing window 67
[task 2019-12-02T17:50:44.497Z] 17:50:44 INFO - {'actions': [{u'type': u'none', u'id': u'0', u'actions': [{u'duration': 16, u'type': u'pause'}, {u'duration': 16, u'type': u'pause'}, {u'duration': 16, u'type': u'pause'}]}, {u'type': u'pointer', u'actions': [{u'y': 14, u'x': 23, u'frame': {u'frame': u'window'}, u'type': u'pointerMove', u'origin': {'element-6066-11e4-a52e-4f735466cecf': u'83da52d0-b516-48d0-ba42-486f2feeee46', 'chromeelement-9fc5-4b51-a3c8-01716eedeb04': u'83da52d0-b516-48d0-ba42-486f2feeee46'}}, {u'button': 0, u'type': u'pointerDown'}, {u'button': 0, u'type': u'pointerUp'}], u'parameters': {u'pointerType': u'mouse'}, u'id': u'1'}]}
[task 2019-12-02T17:50:44.533Z] 17:50:44 INFO - PID 28746 | 1575309044525 Marionette WARN TimedPromise timed out after 16 ms: stacktrace:
[task 2019-12-02T17:50:44.533Z] 17:50:44 INFO - PID 28746 | bail@chrome://marionette/content/sync.js:237:64
[task 2019-12-02T17:50:44.549Z] 17:50:44 INFO - PID 28746 | 1575309044544 Marionette WARN TimedPromise timed out after 16 ms: stacktrace:
[task 2019-12-02T17:50:44.549Z] 17:50:44 INFO - PID 28746 | bail@chrome://marionette/content/sync.js:237:64
[task 2019-12-02T17:50:44.566Z] 17:50:44 INFO - PID 28746 | 1575309044561 Marionette WARN TimedPromise timed out after 16 ms: stacktrace:
[task 2019-12-02T17:50:44.567Z] 17:50:44 INFO - PID 28746 | bail@chrome://marionette/content/sync.js:237:64
[task 2019-12-02T17:50:44.583Z] 17:50:44 INFO -
[task 2019-12-02T17:50:44.583Z] 17:50:44 INFO - TEST-PASS | /dom/events/Event-dispatch-redispatch.html | Redispatching DOMContentLoaded event after being dispatched
[task 2019-12-02T17:50:44.584Z] 17:50:44 INFO - TEST-UNEXPECTED-FAIL | /dom/events/Event-dispatch-redispatch.html | Redispatching mouseup event whose default action dispatches a click event - assert_true: mouseup and click events should've been fired expected true got false
[task 2019-12-02T17:50:44.585Z] 17:50:44 INFO - testMouseUpAndClickEvent/</<@http://web-platform.test:8000/dom/events/Event-dispatch-redispatch.html:117:22
[task 2019-12-02T17:50:44.585Z] 17:50:44 INFO - Test.prototype.step@http://web-platform.test:8000/resources/testharness.js:1984:25
[task 2019-12-02T17:50:44.585Z] 17:50:44 INFO - testMouseUpAndClickEvent/<@http://web-platform.test:8000/dom/events/Event-dispatch-redispatch.html:116:36
[task 2019-12-02T17:50:44.585Z] 17:50:44 INFO - ..
[task 2019-12-02T17:50:44.586Z] 17:50:44 INFO - TEST-OK | /dom/events/Event-dispatch-redispatch.html | took 659ms

This appears to be a consistent failure that began cropping up on ubuntu1804 image from November 29, 2019 push:
https://treeherder.mozilla.org/#/jobs?repo=try&group_state=expanded&resultStatus=testfailed%2Cbusted%2Cexception%2Cretry%2Cusercancel%2Crunning%2Cpending%2Crunnable&searchStr=web-platform-test%2Clinux64&revision=b02d05a8441067ee2a6fb5ecd83ed3433bcb71c5\

:masayuki - would it be acceptable to add a clause in the manifest file as follows?
if os == 'linux' and version == '18.04': FAIL

Flags: needinfo?(masayuki)

Do you reproduce it on local environment? If no, I think that it's really odd bug of our driver or test environment. If yes, I could investigate the odd failure reason. Anyway, it's okay to mark it as FAIL.

Flags: needinfo?(masayuki)

(In reply to Masayuki Nakano [:masayuki] (he/him)(JST, +0900) from comment #2)

Do you reproduce it on local environment? If no, I think that it's really odd bug of our driver or test environment. If yes, I could investigate the odd failure reason. Anyway, it's okay to mark it as FAIL.

I will attempt to reproduce this in an ubuntu1804 virtual machine, but I may require your assistance to do so if something unexpected arises.

I've set up a virtual machine with ubuntu1804, configured and performed an artifact build of firefox with current mozilla-central d1001fea6e4c.

With no changes made to the underlying OS other than apt-get update && apt-get upgrade, and necessary build items installed, this is what I got:

 0:20.88 TEST_END: Test OK. Subtests passed 4/4. Unexpected 0
 0:20.88 INFO Pausing until the browser exits
 1:04.85 INFO No more tests
 1:05.27 pid:8968 1575409760493	Marionette	INFO	Stopped listening on port 39345
 1:05.97 INFO Browser exited with return code 0
 1:05.97 INFO PROCESS LEAKS None
 1:05.97 INFO PROCESS LEAKS None
 1:05.97 INFO Closing logging queue
 1:05.97 INFO queue closed
 1:05.97 INFO PROCESS LEAKS None
 1:05.97 INFO Got 0 unexpected results
 1:05.97 SUITE_END

web-platform-test
~~~~~~~~~~~~~~~~~
Ran 5 checks (4 subtests, 1 tests)
Expected results: 5
Unexpected results: 0
OK
 1:06.09 INFO Closing logging queue
 1:06.09 INFO queue closed

So it's something to do with the environment, or other tests are interfering with this specific test.


For comparison, I re-ran the test directory again to see if other tests are interfering with this particular test:

 1:03.50 TEST_END: Test OK. Subtests passed 1/1. Unexpected 0
 1:03.50 TEST_START: /dom/events/Event-dispatch-redispatch.html
 1:03.53 INFO Closing window 68
 1:07.09 INFO {'actions': [{u'type': u'none', u'id': u'0', u'actions': [{u'duration': 16, u'type': u'pause'}, {u'duration': 16, u'type': u'pause'}, {u'duration': 16, u'type': u'pause'}]}, {u'type': u'pointer', u'actions': [{u'y': 14, u'x': 17, u'frame': {u'frame': u'window'}, u'type': u'pointerMove', u'origin': {'element-6066-11e4-a52e-4f735466cecf': u'f7216c3d-9388-4c24-8866-2b2515dd26f0', 'chromeelement-9fc5-4b51-a3c8-01716eedeb04': u'f7216c3d-9388-4c24-8866-2b2515dd26f0'}}, {u'button': 0, u'type': u'pointerDown'}, {u'button': 0, u'type': u'pointerUp'}], u'parameters': {u'pointerType': u'mouse'}, u'id': u'1'}]}
 1:07.24 pid:9266 1575409920644	Marionette	WARN	TimedPromise timed out after 16 ms: stacktrace:
 1:07.24 pid:9266 bail@chrome://marionette/content/sync.js:237:64
 1:07.30 pid:9266 1575409920697	Marionette	WARN	TimedPromise timed out after 16 ms: stacktrace:
 1:07.30 pid:9266 bail@chrome://marionette/content/sync.js:237:64
 1:07.36 pid:9266 1575409920763	Marionette	WARN	TimedPromise timed out after 16 ms: stacktrace:
 1:07.36 pid:9266 bail@chrome://marionette/content/sync.js:237:64
 1:07.51 TEST_END: Test OK. Subtests passed 4/4. Unexpected 0
 1:07.51 TEST_START: /dom/events/Event-dispatch-reenter.html
 1:07.51 INFO Closing window 70

So it seems, at least in the virtual machine environment, this test passes without any issue.

With this information, do you have any other avenues to investigate? I wonder if it may tangentially be related to bug 1543337? Or perhaps mouse events in the ubuntu1804 image is experiencing issues.

If you're OK with the test being marked as FAIL for ubuntu1804, and it begins passing again, at least the web-platform-test harness will inform us that something has changed.

Flags: needinfo?(masayuki)
Assignee: nobody → egao
Pushed by egao@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/99322b80337f
mark /dom/events/Event-dispatch-redispatch.html as expected failure on ubuntu1804 r=masayuki
Flags: needinfo?(masayuki)

Removing assignment since the bug is now marked as expected failure.

Assignee: egao → nobody
Keywords: leave-open
You need to log in before you can comment on or make changes to this bug.