Bug 1440252 - Implement MediaEngineWebRTCMicrophoneSource::GetSettings. r=padenot MozReview-Commit-ID: IVbax9Xxs8R

Bug 1440968 - Turn on some of the talos tests for QuantumRender on windows. r=jmaher MozReview-Commit-ID: JGXW63ohn8W

Bug 1440968 - Use a different method for skipping talos tests on windows. r=jmaher Having both .*-qr/.* and windows.* as patterns in the run-on-projects test platform list means that a platform like windows10-64-qr matches both and the parser complains. Instead of doing this, we can remove the windows patterns and take the talos tests out of the windows-talos test-set which accomplishes the same thing. MozReview-Commit-ID: 9kMooiNiHTb

Bug 1410456 - Update cubeb from upstream to b1ee1ce. r=padenot MozReview-Commit-ID: 5PmGUcxB6jv

Bug 1410456 - Add new files in update.sh script. r=padenot MozReview-Commit-ID: GD8CHTM1pV8

Bug 1410456 - Keep the old mechanism for the older versions that jni method is not available. r=padenot MozReview-Commit-ID: IsAOhDkNjHp

Bug 1410456 - get mixer latency from JNI instead of system library. r=jchen,padenot,snorp MozReview-Commit-ID: 3YciuVu25JO

Bug 1410456 - remove preferred sample rate implementation because makes use of dlopen. r=padenot MozReview-Commit-ID: jBZ3oewbjh

Bug 1410456 - remove get latency implementation because makes use of dlopen. r=padenot MozReview-Commit-ID: 1Mc2dSk0hlc

Bug 1410456 - remove get min latency implementation because makes use of dlopen. r=padenot MozReview-Commit-ID: CD2FCiMobWm

Bug 1410456 - remove an unused variable that produces a compile warning. r=padenot MozReview-Commit-ID: Hf7Od37bnzX

Bug 1410456 - use jni methods in place of removed cubeb methods. r=padenot MozReview-Commit-ID: 18fQVZeYAgk

Bug 1410456 - Allow OMT access to Android system audio properties. r=esawin MozReview-Commit-ID: 4YkiuzNkNu5

Bug 1439673 - Fix React 16 warnings r=nchevobbe I believe this fixes all warnings except for one. This warning appears the first time the memory panel is selected: "Warning: Failed prop type: Calling PropTypes validators directly is not supported by the `prop-types` package. Use `PropTypes.checkPropTypes()` to call them. Read more at http://fb.me/use-check-prop-types in MemoryApp (created by Connect(MemoryApp)) in Connect(MemoryApp) (created by bound createElementWithValidation) in bound createElementWithValidation in Provider" This appears to be an issue with `devtools/client/memory/app.js` but I will log a new bug for this. MozReview-Commit-ID: 341zdQyfgrN

Bug 1353461 - Mark toolkit/content/tests/reftests/bug-442419-progressmeter-max.xul fails on Windows, r=jmaher This test is already marked fails-if on Windows 8 and all OSX. With run-by-manifest enabled it also starts failing on Windows 7 and 10. The fix will be tracked in bug 1439988. MozReview-Commit-ID: 14xidhwXCue

Bug 1353461 - Increase fuzzy-if for layout/reftests/svg/foreignObject-form-theme.svg with webrender, r=jmaher This test already has a fuzzy-if annotation with webrender, but when run-by-manifest is enabled, the fuzz increases. The fix will be tracked in bug 1439980. MozReview-Commit-ID: 14xidhwXCue

Bug 1353461 - Chunk OSX debug reftests to 3, r=jmaher With run-by-manifest, the debug reftests timeout on OSX. Increasing the chunks by 1 seems to improve them. MozReview-Commit-ID: 14xidhwXCue

Bug 1353461 - [reftest] Implement run-by-manifest for reftest, r=jmaher Run-by-manifest is a mode where we restart Firefox between every manifest of tests. It sacrifices a little bit of runtime for better test isolation and improved stability. This turns run-by-manifest on for all platforms except Android. It also skips jsreftests and crashtests for now (mostly to limit the scope of what was landing all at once). Follow-ups will be filed to get it turned on in those places. MozReview-Commit-ID: DmvozAIPE5Q

Bug 1353461 - [reftest] remove the start-after-crash feature, r=jmaher The point of start-after-crash was to resume running tests after a crash so we don't miss out on test coverage when a crash happens. Now that we're close to landing run-by-manifest, this feature is as necessary since only tests that appear later in the same manifest as the crashing test will be skipped. Another reason to remove it, is that it's current implementation is buggy. It assumes tests have a unique ID (they don't), which means we could accidentally get into an infinite loop if the wrong test happens to crash at the wrong time. A third reason to remove it is that it adds a lot of complexity to the harness. Especially now with run-by-manifest, supporting both would require handling a lot of different edge cases and make things much more complicated than the already are. All that being said, it would still provide value. Not only would it allow us to resume tests in the same manifest, but run-by-manifest isn't yet enabled on Android, jsreftest or crashtest (though we hope to get it enabled in those places in the future). So it may be worth re-implementing start-after-crash again based on the new manifest parsing mechanism that run-by-manifest uses. It should be possible to implement it a lot more cleanly now. This work will have to be left to a follow-up. MozReview-Commit-ID: P2hh5VecKW

Bug 1353461 - [manifestparser] Implement a chunk_by_manifest algorithm, r=jmaher This implements a chunk_by_manifest algorithm. It is similar to chunk_by_slice in that it tries to make an even number of tests run in each chunk. However, unlike chunk_by_slice it will guarantee that tests in the same manifest will all run in the same chunk. This makes it suitable to use with run-by-manifest. This means the chunks won't be perfect (as manifests are differnet sizes). It is also prone to more randomization, similar to chunk-by-runtime. In fact, this algorithm is nearly identical to the chunk-by-runtime one, so it was refactored out to a base class. MozReview-Commit-ID: HI2ByxW0i8V