The service would be restarted after System.exit(0) which would show the crash
feedback form again to the user.
That System.exit(0) was initially used to prevent a silent ANR because of the
Service being started from background on Android Oreo+ without a foreground
notification.
To overcome all this we'll also use a foreground notification on Android Oreo+
but with NotificationManager.IMPORTANCE_LOW to be non-intrusive.
Differential Revision: https://phabricator.services.mozilla.com/D36746
--HG--
extra : moz-landing-system : lando
Some tests still disabled due to either test environment weirdness or actual breakage.
Differential Revision: https://phabricator.services.mozilla.com/D36531
--HG--
extra : moz-landing-system : lando
Because IPC call runs asynchronously in both remote decoder process and
content process, ProcessOutput() for buffers prior to Flush() could be
scheduled to run after the flush promise is resolved, and Codec.queueInput()
could be preempted and processes prior sample after flush.
To help check the validness of buffers, a session ID increased by flush
is added to both RemoteDataDecoder and remote codec service and will be
passed through IPC. If the passed ID doesn't agree with current session
ID, it means the buffer doesn't belong to current session and should be
discard.
Differential Revision: https://phabricator.services.mozilla.com/D36382
--HG--
extra : moz-landing-system : lando
Some tests still disabled due to either test environment weirdness or actual breakage.
Differential Revision: https://phabricator.services.mozilla.com/D36531
--HG--
extra : moz-landing-system : lando
For content like:
<select>
<optgroup style="overflow: scroll">
<option>
the existing rules would match the <xul:scrollbar> elements that are
generated for the <optgroup>, since they use descendant selectors after
the `select:not([size]):not([multiple])`, even though the intention
(probably!) is to match only the scrollbars created for the <select>
itself.
On Android, we don't actually render <select> elements in the page;
instead we use some system UI popup. So in practice the difference in
rendering here isn't relevant. (It's possible we could remove these
rules entirely.)
Differential Revision: https://phabricator.services.mozilla.com/D36449
--HG--
extra : moz-landing-system : lando
Because IPC call runs asynchronously in both remote decoder process and
content process, ProcessOutput() for buffers prior to Flush() could be
scheduled to run after the flush promise is resolved, and Codec.queueInput()
could be preempted and processes prior sample after flush.
To help check the validness of buffers, a session ID increased by flush
is added to both RemoteDataDecoder and remote codec service and will be
passed through IPC. If the passed ID doesn't agree with current session
ID, it means the buffer doesn't belong to current session and should be
discard.
Differential Revision: https://phabricator.services.mozilla.com/D36382
--HG--
extra : moz-landing-system : lando
We don't run any tests on these builds, since they are just used to
generate the profile data for the final build. We can save some time by
skipping all test related code.
Differential Revision: https://phabricator.services.mozilla.com/D36511
--HG--
extra : moz-landing-system : lando
This patch works around a case where the node that we want to set a11y
focus to is input focused, and the gecko a11y virtual cursor is set to
it.
In gecko a11y we don't have a distinction of hover/a11y focus like in
Android, the virtual cursor is already set to the position through the
explore by touch and sends a HOVER_ENTER to android. An accessibility
service will typically listen for thos events and then explicitly
request a11y focus on the node. Since it is internally already set, it
would result in a no-op and no event will be dispatched.
Differential Revision: https://phabricator.services.mozilla.com/D36141
--HG--
extra : moz-landing-system : lando
Now checking the global view tree observer to see if it's alive in order to unsubscribe from further
notifications.
Differential Revision: https://phabricator.services.mozilla.com/D36485
--HG--
extra : moz-landing-system : lando
Create test entries via update introduces performance overhead.
We can store them directly in LookupCache and do not save test entries
to disk.
Differential Revision: https://phabricator.services.mozilla.com/D34576
--HG--
extra : moz-landing-system : lando
Reusing sessions doesn't actually save that much time and avoids a lot of
hard-to-debug intermittents.
Differential Revision: https://phabricator.services.mozilla.com/D32578
--HG--
extra : moz-landing-system : lando
Sometime the geolocation test fails because the position is not retrieved
quickly enough, this is OK as we're just trying to make sure that the
permission is correct.
Differential Revision: https://phabricator.services.mozilla.com/D32576
--HG--
extra : moz-landing-system : lando