Bug 1291715 - Add mochitest for DTMF; r?jib MozReview-Commit-ID: 4acq5uMLxe9

Bug 1291715 - Add support for 44100 and 48000 Hz sample rates to DtmfInband; r?jesup The DtmfInband class does not support sample rates above 32000. This adds support for 44100 and 48000. The 'a' coefficients were calculated in python as: int(round(32768*math.cos(2*math.pi*f/fs))) The 'ym2' coefficients were calculated in python as: int(round(16383*math.sin(2*math.pi*f/fs))) where f was in: [697, 770, 852, 941, 1209, 1336, 1477, 1633] and fs was in: [8000, 16000, 32000, 44100, 44800]. The calculated values were slightly off the existing values at 8000 Hz, but agreed at 16000 and 32000 Hz. MozReview-Commit-ID: GIzyUSyecR4

Bug 1291715 - Add DTMF support to PeerConnection and AudioConduit; r?jib MozReview-Commit-ID: LNN1HNJicCj

Bug 1291715 - Add RTCDTMFSender to PeerConnection.js; r=jib MozReview-Commit-ID: 4vm6c5Chjof

Bug 1291715 - Add RTCDTMFSender and RTCDTMFToneChangeEvent to webidl; r=smaug MozReview-Commit-ID: FvAp6DQex02

Bug 1294812: Canvas shouldn't be accelerated if composition isn't. r?dvander MozReview-Commit-ID: HFHMHjb9KrG

Bug 1280573 - Add testing/mozbase to flake8 linter: r?ahal added testing/mozbase to tools/lint/flake8.lint fixed a first batch of PEP8 errors/warnings at first the commad autopep8 -i --max-line-length 99 -r -j 8 . has been used to fix simpler problems, run from testing/mozbase some of the issues can not easily fixed : - undefined 'names' in code for example isLinux - isLinux and isBsd "fixed" with # noqa - undefined 'message' resolved with return fmt.format(... - undefined 'structured' resolved replacing those with mozlog - long comments - some remaining - addressed with # noqa - package level import everything - addressed with # flake8: noqa restored testing/mozbase/mozdevice/mozdevice/Zeroconf.py fixed issues reported on mozreview fixed ')' in testing/mozbase/mozprocess/mozprocess/qijo.py imports finally fixed multiline string at testing/mozbase/manifestparser/tests/test_manifestparser.py:114 ^^^ and again, but now with ./mach python-test --path-only testing/mozbase/manifestparser/tests/test_manifestparser.py passing fixed testing/mozbase/manifestparser/tests/test_convert_directory.py assert MozReview-Commit-ID: 1FpJF54GqIi

Bug 1305567 - Use base64url encoding, avoid cutting the state and dump download error message. r=francois. MozReview-Commit-ID: 1umDhxY5eKl

Bug 1305120: CPU microcode as a separate field in the crash report. r?ted.mielczarek MozReview-Commit-ID: AN2okOxwTrr

Bug 1274980 part 2: Support Mac OS tests in tc intree config. r=dustin We add support for Mac OSX tests in Taskcluster by support taskcluster-worker macosx engine. We also add a new configuration blob-upload-branch needed by mochitest-other. MozReview-Commit-ID: 6xDpLss0W0N

Bug 1274980 part 1: Add support for test platform regex match. r=dustin Often we need to setup a test configuration for different platforms, but not for different platform builds (opt/debug). This leads to cumbersome configuration duplicates. This patch adds support for platform regular expression matching. For example, if you want to configure the chunk size for linux64 platform both for opt and debug, originally you would do this: chunks: by-test-platform: linux64/opt: 4 linux64/debug: 4 default: 8 With regular expression matching, you only need: chunks: by-test-platform: linux64/.*: 4 default: 8 This patch was originally written by Geoffrey Brown for Windows support. MozReview-Commit-ID: 4hXWWlCMcg2

Bug 1299216 - Remove always parameter from do_process_check decorator. Removing the always parameter which is kinda useless here. Originally it was added to call check_for_crash() in case of a MarionetteException happening. But such an exception is never thrown in case of crashes. It will always be an IOError. So lets get it removed and ensure we call check_for_crashes() in all the cases, and can feed the crash status into the call to handle_socket_failure(). MozReview-Commit-ID: JeK3X7voocD

Bug 1299216 - Enhance handling of chrome and content crashes in Marionette. There are currently various issues in Marionette which cause extra and unnecessary logging output in case of chrome and content crashes. Especially the latter ones are not easy to discover. This patch makes the following improvements: * Correctly handle content process crashes and kill the process with a proper failure message. After the process has been started again the next test will be executed. Because our installed framescripts will no longer be reachable, a restart is necessary to ensure a proper initial state for the next test is available. * Correctly mark chrome process crashes as IOError test failure. Until now we have only used the "Process has been closed" message, which does not correctly cover it, especially not if the process shutdown without a crash. * Allow changing the socket_timeout for the socket client. This was mainly necessary to allow unit tests to run faster. * Collect the number of crashes so it's known even later if the process has been crashed during the current session. It also fixes the case when check_for_crash() gets called twice, and for the second time False is returned which will trigger an invalid code path. * Reduce code duplication when destroying a session. * Adding a unit test to verify the correct behavior for chrome and content crashes. MozReview-Commit-ID: KdUQuJqFRli

Bug 1299216 - Don't care about socket not connected for sock.shutdown() call. MozReview-Commit-ID: 9DXLY66KqTg

Bug 1299216 - Bump mozrunner version to 6.13. MozReview-Commit-ID: 2hCytAyqfsp

Bug 1299216 - [mozrunner] check_for_crashes() has to return the crash count since its last invocation. Adapt check_for_crashes() for latest mozcrash changes, which returns the number of crashes for both log_crashes() and check_for_crashes() now. Also the runner should accumulate the number of crashes so it will be known at any time how many times the process has been crashed. MozReview-Commit-ID: Dl9FlH1TalH

Bug 1299216 - [mozcrash] Count crash reports in check_for_crashes and bump version to 1.0. Currently check_for_crashes() behaves differently compared to log_crashes(), whereby it only returns a boolean if a crash has been detected but not the amount of crash reports found. We should make sure that both methods behave the same. Given that this change might affect consumers, we should have a major version bump for the new release. MozReview-Commit-ID: LiPaozJL5NF

Bug 1274980 part 2: Support Mac OS tests in tc intree config. r=dustin We add support for Mac OSX tests in Taskcluster by support taskcluster-worker macosx engine. We also add a new configuration blob-upload-branch needed by mochitest-other. MozReview-Commit-ID: 1NoqdYS97va

Bug 1274980 part 1: Add support for test platform regex match. r=dustin Often we need to setup a test configuration for different platforms, but not for different platform builds (opt/debug). This leads to cumbersome configuration duplicates. This patch adds support for platform regular expression matching. For example, if you want to configure the chunk size for linux64 platform both for opt and debug, originally you would do this: chunks: by-test-platform: linux64/opt: 4 linux64/debug: 4 default: 8 With regular expression matching, you only need: chunks: by-test-platform: linux64/.*: 4 default: 8 This patch was originally written by Geoffrey Brown for Windows support. MozReview-Commit-ID: He95s5WYXsT

Bug 1274980 part 2: Support Mac OS tests in tc intree config. r=dustin We add support for Mac OSX tests in Taskcluster by support taskcluster-worker macosx engine. We also add a new configuration blob-upload-branch needed by mochitest-other. MozReview-Commit-ID: HKVWTWuF12s