Bug 1453396 - Tests splitted into two to fix intermittent test timed out. r=ckerschb

Bug 1462650 - Improve imgTools::EncodeScaledImage performance. r=lsalzman We should avoiding creating a DrawTarget to create a new DataSourceSurface when the original surface produced by RasterImage::GetFrameAtSize matches our requirements in imgTools::EncodeScaledImage. We should also be using Skia instead of Cairo. This patch also fixes a few error conditions where we would not have unmapped the surface properly.

Bug 1463767 - ReleasingTimerHolder should expose nsINamed::GetName only if MOZ_COLLECTING_RUNNABLE_TELEMETRY is defined, r=smaug

Bug 1461727 - The name of the type field in the type descriptor for WebAssembly.Global shall be "value". r=lth. The current name is "type". Henceforth it shall be known as "value", per CG decision of 15 May 2018.

No bug - Fix some bogus indentation. r=me MozReview-Commit-ID: 6G7oS6MkJ0Y

No bug - Use a static atom instead of a dynamic one. r=me MozReview-Commit-ID: CUTwfsCrovQ

Backed out changeset 5bb547481faf (bug 1451973) for testChild failures on a CLOSED TREE

Bug 1265584 - Update wpt metadata, r=maja_zf MozReview-Commit-ID: F0KYHBJ8nIh

Bug 1265584 - Add a test for wpttest metadata, r=maja_zf MozReview-Commit-ID: Jme9GND8ihS

Bug 1265584 - Output asserts to wptreport.json, r=maja_zf In the future we want to update metadata using the wptreport.json data, since that's much much smaller and easier to parse. In addition, this is required to determine if a test fully passed, so it makes sense to store it here. MozReview-Commit-ID: ErYT33BhqGg

Bug 1265584 - Use ujson where possible for faster metadata update, r=maja_zf Profiling shows that switching to this library means we no longer spend most of the update time parsing json (vs 80% or so before), making other optimisations worthwhile. This is never used in automation (except wptsync) so availability of the library in the internal pypi isn't a problem. MozReview-Commit-ID: U5gabb5lz8

Bug 1265584 - Support updating asserts with wpt-update, r=maja_zf With support for asserts, it's also necessary to be able to update the expected number of asserts automatically using wpt-update. Unfortunately asserts don't work quite like test statuses, so this involves a reasonable amount of refactoring. For asserts the desired behaviour is that the max asserts is either one plus the highest recorded number of asserts, or the current value, whichever is higher, and for the minimm asserts, it's the minumum of the current value and one lower than the lowest recorded value (clamped at zero). Instead of creating per-platform expectations, the code only updates the defaults (or any existing conditional that happens to match). It's not clear that we have enough information to meaningfully make per-platform expectations, and we want to reduce the risk of intermittents. MozReview-Commit-ID: HuTpbAZYGzo

Bug 1265584 - Reverse the order of metadata iteration, r=maja_zf wptrunner previously iterated over properties from least significant to most significant. However this was broken since it caused per-directory properties to override per-test properties, which wasn't expected. Therefore we reverse the order of iteration from most significant to least. MozReview-Commit-ID: 5Rh6EGNtnUS

Bug 1265584 - Add support for recording asserts in wptrunner, r=ato, maja_zf Gecko has an API for producing a non-fatal "assert". For quality control, it should be possible to annotate the range of possible numbers of these asserts produced during a test execution, and fail if the actual number of asserts falls outside this range. This patch adds assert checking by default in debug builds. It adds two metadata properties; max-asserts and min-asserts for specifying the range of possible asserts produced in a test. MozReview-Commit-ID: BFiIfYKuB9L

Bug 1265584 - Make base_executor_kwargs arguments match executor_kwargs, r=ato MozReview-Commit-ID: IS7KwuRjmc6

Bug 1265584 - Move wptrunner marionette usage onto a single thread, r=ato Running marionette on a background thread is problematic in the case that a test times out. In this case the background thread is not terminated. If we then call into marionette again on the main thread we may race with something that happens on the runner thread. The marionette client isn't threadsafe, so this leads to buggy behaviour. The simplest fx for the problem is just to move all the marionette calls onto the main thread and instead of waiting on the main thread, spin up a thread with a timer. MozReview-Commit-ID: 3vVlMcwPHSx

Bug 1265584 - Fix logging of unexpected assertions with mach formatter, r=ahal MozReview-Commit-ID: Dk1ahUYyYIm

Bug 1382683 - Part 3. Add gtests for SurfaceFilter/Pipe::WritePixelBlocks. r=tnikkel

Bug 1382683 - Part 2. Switch nsGIFDecoder2 to write pixels in blocks instead of individually. r=tnikkel nsGIFDecoder2::YieldPixel is sufficiently complex that the optimizer does not appear to inline it with the rest of the templated methods. As such there is a high cost to calling it. This patch modifies it to yield a requested number of pixels before exiting, allowing us to amortize the cost of calling across a row instead of a pixel. Based on profiling, this will significantly reduce the time require to decode a frame.

Bug 1382683 - Part 1. Implement SurfacePipe::WritePixelBlocks for faster writing of pixels. r=tnikkel It has been observed in profiling that the templated methods that write pixels to an image buffer do not always inline methods properly, leading to a high cost of writing a single pixel if it is less than trivial. As such, there is a new SurfacePipe method, WritePixelBlocks, which requests pixels in blocks. The provided lambda will write up to the requested number of pixels into the given buffer. WritePixelBlocks itself will request enough pixels to fill the row, advance the row if complete and iterate until it is complete or we need more data.