Changes:
- reduced `linux64/debug` chunking to 14 (from 16)
- reduced `linux64-ccov/debug` to 14 (from 16)
- increased `windows64-ccov` to 16 (from 10)
- maintain all non-ccov debug to 8
- maintain all asan to 8
- reduce everything else to 5
Differential Revision: https://phabricator.services.mozilla.com/D30303
--HG--
extra : moz-landing-system : lando
These ini files are all empty, which didn't include any extra information for testing, so we should remove them.
Differential Revision: https://phabricator.services.mozilla.com/D30437
--HG--
extra : moz-landing-system : lando
Create a new IPDL message `ShutdownComplete`, direction from parent (RDD) to child (content), to inform the child when the decoder shutdown has been completed. The remote decoder child uses that message to resolve the shutdown promise.
Differential Revision: https://phabricator.services.mozilla.com/D28340
--HG--
extra : moz-landing-system : lando
This replaces the various Debugger-related member classes in
js::CrossCompartmentKey with a series of small structs that can be used directly
as alternatives in CrossCompartmentKey::WrappedType. Thus, instead of having a
two-level tag --- the Variant tag, and then for DebuggerAndObject case, a
DebuggerObjectKind value --- the Variant tag can do all the work by itself.
This also tightens up the types a bit: choosing the wrong DebuggerObjectKind
would be a silent error, but using the wrong constructor might get you a type
error (although unfortunately some of the types are not as specific as you might
hope: NativeObject instead of WasmInstanceObject, for example).
A new comment explains the rationale for giving Debugger API objects entries in
the wrapper map.
Differential Revision: https://phabricator.services.mozilla.com/D28781
--HG--
extra : moz-landing-system : lando
In patch2, whenever the media element's readyState is changed back to HAVE_NOTHING, we would reset all cues' active flag and update cue display in order to hide them.
It also means that we should not set any cue's flag when media element's readyState is `HAVE_NOTHING`, so we should abort the `TimeMarchesOn` in this situation.
Differential Revision: https://phabricator.services.mozilla.com/D30390
--HG--
extra : moz-landing-system : lando
All changes are reversible upon reboot, with exception of the animation setting which is restored to default settings once Raptor concludes testing.
All values are for Pixel 2. Motorola G5 patch will be available separately.
Changes:
- set cpu/gpu to `performance` mode, and override minimum frequency with the maximum available frequency
- tweak msm-bus related kernel settings
- set display to be permanently on when connected over USB
- disable animation for duration of test
- turn off thermal throttling
Differential Revision: https://phabricator.services.mozilla.com/D30116
--HG--
extra : moz-landing-system : lando
- Make process the second level menu of (Scalars, Keyed Scalars, Histograms, Keyed Histograms and Events)
- Change the process dropdown to be a store dropdown
- Main store is selected by default
- Added a label before the store dropdown
- Refactor a bit the code to avoid lot of duplications
Note: This revision should be way cleaner
Differential Revision: https://phabricator.services.mozilla.com/D29483
--HG--
extra : moz-landing-system : lando
Amend several test files for triggering eval() assertion through simpletest.js
Differential Revision: https://phabricator.services.mozilla.com/D30474
--HG--
extra : moz-landing-system : lando
This patch doesn't port all of the existing tests because some of them
do not pass yet and some others need more work to be ported. This will
happen in follow-up bugs.
Differential Revision: https://phabricator.services.mozilla.com/D30401
--HG--
rename : toolkit/components/antitracking/test/browser/storageprincipal_head.js => toolkit/components/antitracking/test/browser/dynamicfpi_head.js
extra : moz-landing-system : lando
This API abstracts away the details of the decision on what context should be
partitioned away from the consumers and centralizes the decision making into
the same location in the code base.
Differential Revision: https://phabricator.services.mozilla.com/D29742
--HG--
extra : moz-landing-system : lando
This StorageAccess code tells callers that they must partition third-party
storage, or deny storage access if that is not possible.
Differential Revision: https://phabricator.services.mozilla.com/D29740
--HG--
extra : moz-landing-system : lando
The policy that this patch implements in the antitracking backend is to treat
third-party trackers exactly the same way as BEHAVIOR_REJECT_TRACKER, and
additionally partition all third-party contexts as well.
Differential Revision: https://phabricator.services.mozilla.com/D29738
--HG--
extra : moz-landing-system : lando
This error code indicates the specific case where the antitracking backend
rejects a particular access request because the resource is third-party and
the cookie policy mandates that third-party resources must be partitioned.
Differential Revision: https://phabricator.services.mozilla.com/D29737
--HG--
extra : moz-landing-system : lando
This new code designates our new cookie policy for blocking cookies and
storage access from third-party trackers and partitioning the cookie jar
of the rest of third-party resources.
Differential Revision: https://phabricator.services.mozilla.com/D29736
--HG--
extra : moz-landing-system : lando
Try to further reduce flicker by increasing the time we keep stale results visible.
Differential Revision: https://phabricator.services.mozilla.com/D30502
--HG--
extra : moz-landing-system : lando
The client_id part of browser_html_discover_view_clientid.js was failing
on TV because of a pre-existing, test-specific issue in Telemetry.
Fixing this is not trivial, so just check that the ID was set instead of
checking its exact value.
See the comment for more details; the fix will be part of bug 1537933
Differential Revision: https://phabricator.services.mozilla.com/D30001
--HG--
extra : moz-landing-system : lando
- Fill stars based on whether the rating is within the 0.5 range of a
0.5-multiple, rather than checking whether the rating is at least as
large as the 0.5-multiple. This follows the boundaries at:
bb9277eeff/src/ui/components/Rating/index.js (L139-L140)
- Use a review star rating instead of re-using the bookmark star.
This is not necessarily to be more consistent with AMO's stars,
but to prevent the stars from becoming non-stars if we ever change
the bookmark icon. The SVG icon is based on the path at:
bb9277eeff/src/ui/components/IconStar/index.js (L19)
- Turn it into a custom element to make re-use easier.
Differential Revision: https://phabricator.services.mozilla.com/D29480
--HG--
extra : moz-landing-system : lando
