Bug 1411462 - Abort when I/O error seen; r?glandium Before, I/O errors writing to stdout/stderr (e.g. due to broken pipe) would result in handleError() being called and execution would keep running. This would potentially result in an error message for every log/line failure being printed to stderr. We change the behavior so I/O failures are fatal and abort execution. We test the new behavior by changing a test to pipe to `head` directly. Since `head` exits once it has seen sufficient output, this results in an EPIPE which now results in immediate program termination. MozReview-Commit-ID: 1UecZJ56h4r

Bug 1411462 - Add test for `configure --help`; r?glandium We add a simple cram test that `configure --help` works. I added the test to build/tests because I'm not sure where else it should go. This test uncovers a few interesting things: 1) piping `./configure --help` to `head` directly causes a Python traceback (presumably due to the pipe disappearing once N lines have been read) 2) "checking for vcs source checkout" is printed for --help 3) It is printed twice (!!) These will be addressed later. Establishing test coverage is more important. MozReview-Commit-ID: 9zQ5X8ulTkc

Bug 1411462 - Normalize when argument earlier in imply_option(); r?glandium This makes `configure --help` work again (it stopped working due to 370a4a2a7898 (bug 1405982). MozReview-Commit-ID: 2gCmAAsE0qW

Bug 1415772: Implement MNearbyInt recover instruction MozReview-Commit-ID: D7JdEHjDl2W

Bug 1415448 - Move tests from AnimationEffectTiming/getAnimations.html to Animatable/getAnimations.html; r?hiro As well as moving these tests, this patch simplifies them in several cases and tries to make them match the existing tests in that file (e.g. using 'animation' instead of 'anim', using MS_PER_SEC, using assert_array_equals, etc.) MozReview-Commit-ID: Gf7rucG9ml1

Bug 1415448 - Update test descriptions in interfaces/Animatable/getAnimations.html; r?hiro We plan to merge in tests here from AnimationEffectTiming/getAnimations.html so in this patch we update the test descriptions first. MozReview-Commit-ID: 6yK6E0cNTKd

Bug 1415448 - Drop getComputedStyle.html test in interfaces/AnimationEffectTiming; r?hiro This test feels out of place -- there's no getComputedStyle method on AnimationEffectTiming and we generally test timing properties by calling getComputedTiming. This patch moves most of the tests in this file to the corresponding members whose liveness they check while updating them to use getComputedTiming instead. The remaining tests that seek the currentTime and check the style with various values of endDelay should be covered by timing-model/animation-effects/simple-iteration-progress.html MozReview-Commit-ID: 3qyXgJ7qRVy

Bug 1415448 - Tidy up test descriptions for AnimationEffectTiming tests; r?hiro The test descriptions should generally be testable statements. I'm following the convention of BDD-style naming where the subject is implied (e.g. 'Has the default value 0' should be read as '<test subject> has the default value 0'). MozReview-Commit-ID: L2i5AlyIMva

Bug 1415448 - Rename discrete-animation.html test file to discrete-type.html; r?hiro For consistency with visibility-type.html. MozReview-Commit-ID: 5yUGo2X1cNd

Bug 1415448 - Move the tests for the type of the 'visibility' property to the animation-types section; r?hiro MozReview-Commit-ID: WgicxIVrZ3

Bug 1415448 - Rename setTarget.html to target.html; r?hiro This matches better the naming of other test files. MozReview-Commit-ID: 3rzEwBhum3E

Bug 1415448 - Tidy up titles of Web Animations web-platform-tests; r?hiro It's not necessary to say "tests" or "tests for" in the title of these tests. It's obvious from the context that these are test files. This patch: * Remove "Tests for" and "tests" from the titles * Makes the titles match the spec sections they test more closely where practical * Makes the titles more consistent in general (e.g. not putting () after method names) * Updates a few spec links * Drops a few author annotations since we decided to no longer use them There are still some inconsistencies: - The naming of the setTarget.html test file - The location of the effect-value-visibility.html file - The getComputedStyle.html test - etc. These will be fixed in subsequent patches in this series. MozReview-Commit-ID: Ghl0dWalYZE

Bug 1415448 - Update web-platform-tests manifest; r?hiro This is simply the result of running: ./mach wpt-manifest-update MozReview-Commit-ID: EKoDVNn7yA2

Bug 1416067 - Avoid doing a bunch of useless event-regions work for frames with empty border boxes. r?mstange MozReview-Commit-ID: 8gsIJojhQ6t

Bug 1413830 - PART 2: introduce root/parent session_id MozReview-Commit-ID: ATyRNzky8R4

Bug 1413830 - PART 1: track new events for onboarding telemetry; MozReview-Commit-ID: 3jNAmOcrvEa

Bug 1413830 - PART 2: introduce root/parent session_id MozReview-Commit-ID: ATyRNzky8R4

fixup! Bug 1413830 - PART 1: track new events for onboarding telemetry;

Bug 1413830 - PART 1: track new events for onboarding telemetry; MozReview-Commit-ID: 3jNAmOcrvEa

Bug 1412608 - Fix comment selection color in markup view. r=jdescottes MozReview-Commit-ID: 9G5efQSPHCf