when coordinatesRelativeToScreen was made async not everything was made to await properly
Categories
(Core :: Panning and Zooming, defect, P3)
Tracking
()
People
(Reporter: tnikkel, Assigned: dlrobertson)
References
(Regression)
Details
(Keywords: regression, Whiteboard: [lang=c++])
Attachments
(1 file)
Botond noticed this.
For example, synthesizeNativeWheel awaits coordinatesRelativeToScreen but promiseNativeWheelAndWaitForObserver calls synthesizeNativeWheel and it does not await synthesizeNativeWheel.
Updated•3 years ago
|
Comment 1•3 years ago
|
||
Set release status flags based on info from the regressing bug 1725540
Comment 2•3 years ago
|
||
:hiro, since you are the author of the regressor, bug 1725540, could you take a look?
For more information, please visit auto_nag documentation.
Reporter | ||
Comment 3•3 years ago
•
|
||
We'll get to this when we get to it. No need to needinfo hiro. This is a test only function, so this is cleanup and/or fixing potential intermittents only.
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Reporter | ||
Comment 4•3 years ago
|
||
We don't need to track this for any releases, it's test related issue that we can't link to any known intermittents yet.
Comment 5•3 years ago
|
||
Set release status flags based on info from the regressing bug 1725540
Reporter | ||
Comment 6•3 years ago
•
|
||
Ugh, I guess the bot won't let me. Restoring the flags to what they were before. Wish we could just get rid of these flags on this bug so we don't waste time, we don't need to track this for a release.
Updated•3 years ago
|
Reporter | ||
Updated•3 years ago
|
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Comment 7•3 years ago
|
||
Make the APZ mochitests use coor coordinatesRelativeToScreen and its callers
properly. When wwas made async not everything was made to await properly.
Updated•3 years ago
|
Updated•3 years ago
|
Comment 9•3 years ago
|
||
Backed out for causing failures at test_group_scroll_linked_effect.html.
Backout link: https://hg.mozilla.org/integration/autoland/rev/33837286f8d89eb69a7be16c4f30050f8a214ead
Failure log: https://treeherder.mozilla.org/logviewer?job_id=376555511&repo=autoland&lineNumber=7852
Assignee | ||
Comment 10•3 years ago
|
||
I was able to reproduce the failure on a local machine. I'm not entirely sure at the moment why the tests fails, but I'll start to do some debugging on the test.
Updated•3 years ago
|
Updated•3 years ago
|
Comment 11•3 years ago
|
||
Comment 12•3 years ago
|
||
Backed out changeset adf2b25deb64 (Bug 1760986) for causing mochitest fis test failures.
Backout link
Push with failures
Failure Log
Assignee | ||
Comment 13•3 years ago
|
||
Hmm same test failure, but I'm unable to reproduce this now on my local box now. I think I'll back out the changes to that test for now and create a separate issue to fix the async/await usage in the failing test.
Comment 14•3 years ago
|
||
Comment 15•3 years ago
|
||
bugherder |
Comment 16•3 years ago
|
||
Since the status are different for nightly and release, what's the status for beta?
For more information, please visit auto_nag documentation.
Updated•2 years ago
|
Description
•