Bug 1368733 - [taskcluster] Ensure job tasks run automatically on try when they're supposed to, r=dustin The logic here is a bit tricky to grok, but essentially there are two kinds of "job" tasks, those that should always be considered (and possibly be optimized away later due to "skip-unless-changed"), and those that should only be considered if their associated build-platform is also going to be scheduled. If -j is specified, that should supercede both cases. This patch uses the prescence of the 'build_platform' attribute to draw the distinction. MozReview-Commit-ID: H9SjeYuZ8F0

Bug 1367851 - Use ComponentCallbacks to listen for low memory notifications. r=ahunt At the moment, we forward these from GeckoActivity, which means that they won't work if no GeckoActivity-based activity is active (can happen within our settings for example). As of API14, we can now register an app-wide ComponentCallbacks(2) class, allowing us to easily receive low memory notifications no matter which activity is currently alive. MozReview-Commit-ID: 5GjSjsTKxAD

Bug 1368114 - Don't mesure memory added by a notification shown only a few times to the user in AWSY. r=jmaher MozReview-Commit-ID: 78qq7liztWw

Bug 1342794 - Remove broken searchplugin dunaj.sk from Firefox Slovak (sk) r=delphine MozReview-Commit-ID: HaMMNyvgJxr

Bug 1368684 - Stop building webrender-enabled builds in automation. r=dustin As of bug 1342503 being fixed, all of our desktop firefox builds have webrender compiled in by default. Webrender can therefore be enabled at runtime either by a pref or environment variable on any desktop firefox build. The old builds that we originally used to stand up webrender are no longer needed, as the *only* difference between them and the regular builds are that they build with the pref turned on instead of turned off. This doesn't warrant keeping around these extra builds, and this patch removes them along with all the associated goop that was needed to configure them. MozReview-Commit-ID: 5wlOWo11fEk

Bug 1359328 - disable libstdc++ compat check for fuzzing tc build r=aobreja,decoder MozReview-Commit-ID: 4ZgdtnG2ayx

Bug 1359328 - update geck_v2_whitelist.py r=aobreja,decoder MozReview-Commit-ID: HMKKfKbuWEl

Bug 1359328 - Updates for fuzzing taskcluster build r=aobreja,decoder MozReview-Commit-ID: 1RDQYnGTE2s

Bug 1359328 - Add a fuzzing build to taskcluster r=aobreja,decoder MozReview-Commit-ID: BYbycnB5wdV

servo: Merge #16317 - Fix #6799: set stacking_context_position correctly on fragment_border_iterator (from eloycoto:issue6799); r=emilio Hey, First of all, this is my first PR to Servo project and I'm learning Rust, so sorry if you see something that it's not correct. I did that as best as I know. This PR fix the issue #6799; I tried all the corner cases that I can think about it and always get the right result and the same as other browsers. Related to the build: - [x] `./mach build -d` does not report any errors - [x] `./mach test-tidy` does not report any errors - [x] These changes fix #6799 In the other hand, I added the test in the cssom folder, is where getBoundingClientRect is defined, so I think that is the best place. I'm sure that the line 122 can be better, but I didn't find a way to transform a Point2D from f32 to px in a easy way. I'm here to listen to your recommendations and fix any issue. Thanks! Source-Repo: https://github.com/servo/servo Source-Revision: 9d32b9cc35377f5d74197514435199e407c096fa

Bug 1359976: base worker payload generation on worker-type; r=wcosta r=aki To date we have variously specified both worker-type and worker-implementation, often manually coordinated. We also embedded a few awkward assumptions such as that the native engine only runs on OS X. But a worker type has one and only one implementation, and that implementation is stable over time (as changing it would require simultaneous landings on all trees). Instead, this change makes worker-type the primary configuration, and derives both a worker implementation (defining the payload format) and worker OS (determining what to include in the payload) from that value. The derivation occurs when deciding how to implement a particular job, where the run_using functions are distinguished by worker implementation. The two-part logic to determine how and where to run a test task based on its platform is combined into a single transform, `set_worker_type`. This contains some other related changes: - MOZ_AUTOMATION is set in specific jobs, rather than everywhere docker-worker is used - the URL to test packages is factored out into a shared function - docker-worker test defaults are applied in `mozharness_test.py` - the WORKER_TYPE array in `task.py`, formerly mixing two types of keys, is split - the 'invalid' workerType is assigned an 'invalid' implementation - all tasks that do not use job descriptions but use docker-worker, etc. have `worker.os` added Tested to not produce a substantially different taskgraph for a regular push, a try push, or a nightly cron. MozReview-Commit-ID: LDHrmrpBo7I

Bug 1359976: remove references to now-unused test-platform-phylum; r=wcosta MozReview-Commit-ID: A86tEB4nbIx

Bug 1359976: clean out un-handled optionally_keyed_by; r=wcosta While this was allowed by the schema, it would never be resolved, and was unused. MozReview-Commit-ID: LIxJmr9ZSdK

Bug 1368718: rename worker type. r=dustin Rename worker-type to releng-hardware/gecko-t-osx-1010. MozReview-Commit-ID: IgwqgMvmqYb

Merge inbound to m-c. a=merge

Merge m-c to autoland. a=merge

Bug 1350253 - Provide GeckoHlsDemuxerWrapper & corresponding generated JNI files as the glue for HLSDemuxer and GeckoHlsPlayer. r=jolin,jya MozReview-Commit-ID: 62cnGQsmdNS

Bug 1365912 - Add a pref for enabling compact and touch mode. r=dao MozReview-Commit-ID: 1hmTdl0zSKB

servo: Merge #16238 - Implement "update the image data" (from gterzian:implement_update_the_image_data); r=jdm <!-- Please describe your changes on the following line: --> Spec compliant implementation of the [update the image data algorithm](https://html.spec.whatwg.org/multipage/embedded-content.html#update-the-image-data). Currently still a work in progress, the ['async src complete test`](https://github.com/servo/servo/blob/master/tests/wpt/web-platform-tests/html/semantics/embedded-content/the-img-element/img.complete.html#L33) is still passing as it was before, even though I switched to the new code, so I guess that's something. @jdm I will be picking this up next weekend, I left a bunch of TODO and NOTES in the code, if you or someone else have time this week I would appreciate an initial scan and feedback. --- <!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `__` with appropriate data: --> - [ ] `./mach build -d` does not report any errors - [ ] `./mach test-tidy` does not report any errors - [ ] These changes fix #11517 (github issue number if applicable). <!-- Either: --> - [x] There are tests for these changes OR - [ ] These changes do not require tests because _____ <!-- Also, please make sure that "Allow edits from maintainers" checkbox is checked, so that we can help you if you get stuck somewhere along the way.--> <!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. --> Source-Repo: https://github.com/servo/servo Source-Revision: fe7d039416ea93f9a5a120cda9a6114ec1438c3e

Bug 1367839 - Add decrypt(s,ed,ing,able) to the spellcheck dictionary. r=Ehsan MozReview-Commit-ID: 4jyTphO6Ja3