Automatic update from web-platform-testsservice workers: Add long timeout to matchall test (#13684)
clients-matchall-order.https.html is a slow test because it does a lot of navigations.
--
wpt-commits: b3e9536a7ca2a6fbdb732b85275e13cc6d454237
wpt-pr: 13684
Automatic update from web-platform-testsAdd some tests for invalid arguments to WebAssembly.*Streaming.
--
Test some invalid HTTP statuses.
--
Test cross-origin responses for WebAssembly.
--
Add tests for case differences in the wasm content type.
--
Add a test for empty bodies.
--
Add a test for disturbed bodies.
--
Add a test for passing a rejected Promise.
--
Add some tests for instantiateStreaming().
--
wpt-commits: 99e7a8e331555e0637a2cee1bda193093df36d5b, 700452f6412a17cbf5586dfa24047a164661f89c, 939a2b9916c01fe18c5f240c09e27be1ff99f0b7, f0e55e90830a2fdea4e99e5fc019c959c3f7c982, 06c65c738bba5e0587d1bde349b4601dd8b932ac, b47da4fd4f519b1fe8bd77582ed57d2c5129e62d, 2832c5d39c644281ac644428c8d09c2443602eae, 36ed1aa52242875634e4b33a50e3fded2787656d
wpt-pr: 13652
Automatic update from web-platform-testsDon't let outer multicol height confuse orphans/widows on inner multicol.
In the initial layout pass of a multicol container with auto height,
there'll be no known breaks, but we will honor the contraints of any
outer fragmentation context, and insert pagination struts if necessary.
These pagination struts need to be ignored when we calculate the height
requirements imposed by orphans and widows requirements, or we risk
making the inner multicol too tall.
Bug: 891703
Change-Id: Ia9281508fcbba3572d653f1bbf863f045db71827
Reviewed-on: https://chromium-review.googlesource.com/c/1296492
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Emil A Eklund <eae@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#601923}
--
wpt-commits: 7ac0903a5721fbefd4a5e40ab1ad41839cb7d395
wpt-pr: 13682
Automatic update from web-platform-testsRemove unused `channel` argument in `Firefox.version` (#13642)
The only call site is in at the end of `setup_wptrunner` (run.py) where
no `channel` argument is passed. At that point, `setup_kwargs` has
already been called, which guarantees that `kwargs["binary"]` is set, so
even the fallback `self.find_binary(channel)` (where `channel` would be
`None`) is dead code.
--
wpt-commits: b97bfe83f81009ec886f7292664a6582ad28c581
wpt-pr: 13642
Automatic update from web-platform-testsFix the documentation of `action_sequence` somewhat (#13680)
--
wpt-commits: f709c0bcdff406cd539a02cf8c57122f025a16bb
wpt-pr: 13680
Automatic update from web-platform-testsUpdate mozdownload from 1.24 to 1.25 (#13659)
--
wpt-commits: 719e641f65d5f840d017cf03f946fed5e9ba5ebd
wpt-pr: 13659
Automatic update from web-platform-testsFix #13656: make percentage-heights-003 test definiteness (#13667)
--
wpt-commits: 956bd8fc1960bc574dcd1aebf3a33131d05f80b4
wpt-pr: 13667
Automatic update from web-platform-testsAdd an instance of ImageData to the HTML interfaces test.
This causes the test to catch a bug in WebKit, where it defines a "data"
property on the instance, along with the correct property on the prototype.
--
wpt-commits: e7709bb04369254cf0aca11a869a23e1963abdef
wpt-pr: 11751
Automatic update from web-platform-testsUpdate docker image to Ubuntu 18.04 (#13676)
This is the latest LTS release, so it makes sense to test on it. Also it is a requirement
to get servo builds running in the docker image since 16.04 has a too-old gstreamer.
--
wpt-commits: fbc56f388ac5d3a9cfcdfc161917ba0cfa2280f5
wpt-pr: 13676
***
Backed out changeset dfdd63aae0c5 (bug 1505271) for raptor perma failures CLOSED TREE
--HG--
extra : histedit_source : e58f4cd5934b3ac7604780a2e0b9efac5d3a7b20%2C2bc98468bce0d3d29c41473b29e92f43d5f7b7ee
There's a race condition here where we receive STATE_START before we've enabled GeckoViewProgressChild; this patch starts listening for web progress in onInit() rather than onEnable() so that we can guarantee progress tracking will work whenever a ProgressDelegate is set.
Now that h2 is pretty well stable, and we're fairly confident in our hpack table implementation, it's worth hiding this logging without some extra hoops, as it's just a lot of noise in logs.
Differential Revision: https://phabricator.services.mozilla.com/D11406
--HG--
extra : moz-landing-system : lando
When registering dynamic builtin scalars and events (Build Faster support) we
didn't check whether they were expired. Let's do that.
Differential Revision: https://phabricator.services.mozilla.com/D11329
--HG--
extra : moz-landing-system : lando