When compiling C/C++ sources via Rust build scripts there's no point in
enabling warnings-as-errors as all such code is third-party code.
MozReview-Commit-ID: 5pGH6w9ZE2I
--HG--
extra : rebase_source : ad36be6aed39d55055728f85b799adf5f0cf0f4b
This patch changes the various user prompt tests to check if
the command was appropriately run after closing the open
user prompt.
MozReview-Commit-ID: GhbhSa3zNEy
--HG--
extra : rebase_source : 2354cbe7f4e0323098b4223ad89f9da78b9fd696
Automatic update from web-platform-testsUpdate mozinstall from 1.15 to 1.16.0 (#11627)
--
wpt-commits: b305e43f8a9d2a94931d673d90606c1d01d1231f
wpt-pr: 11627
Automatic update from web-platform-testsUpdate certs for hosts changes.
This is required to use the recently added hosts over https.
--
wpt-commits: f2f1b207292a20677b185b828f00a8894188a27d
wpt-pr: 12108
Automatic update from web-platform-testsAdding tests against and fixes for tabs in Server-Timing headers
According to the spec
(https://w3c.github.io/server-timing/#the-server-timing-header-field),
optional whitespace is allowed amongst parameter names and values. We
should be discarding this whitespace during parsing but, when there are
tabs, we were treating it like an error and discarding the whole value.
Changed the code that tokenizes HTTP headers to skip tabs and spaces
when consuming optional whitespace.
BUG=798446
Change-Id: If776761e5ea199e662ec7b2b5aa245e4581131fd
Reviewed-on: https://chromium-review.googlesource.com/1147258
Reviewed-by: Emil A Eklund <eae@chromium.org>
Commit-Queue: Tom McKee <tommckee@chromium.org>
Cr-Commit-Position: refs/heads/master@{#577325}
--
wpt-commits: 4ec913040882c7bb28846a65e7e086785dcf2ab6
wpt-pr: 12149
Automatic update from web-platform-tests[infra] Revert recent reversion to config file
This reverts commit 9f21134354f7d02f1497826d00ba4297ba78c445.
The initial reversion was motivated by an integration issue with the
TaskCluster service. The underlying bug has been corrected [1] making
this changeset suitable for `master`.
[1] https://github.com/taskcluster/taskcluster-github/pull/265
--
wpt-commits: e62afac4c9dac57d8b81d2bf1364694e3d653ff9
wpt-pr: 12151
Automatic update from web-platform-tests[infra] Update to latest configuration file format
The TaskCluster service recently implemented support for a new
configuration file format and deprecated the prior version. The new
format uses the JSON-e templating system [1] to allow for declarative
task generation, and this allows the same tasks to be defined with far
less repetition.
[1] https://taskcluster.github.io/json-e/
--
[infra] Remove code for generating config file
Previously, the TaskCluster configuration file for this project included
a large amount of duplication. This motivated the creation of a script
to generate the file procedurally. A recently-released configuration
file format made it possible to express the same tasks with far less
duplication, obviating the need for this script.
--
wpt-commits: ce345fbbc3929361d15e8bcceec6a7a7123af5bc, c8f456094ec0b31d11e1601082d2f76268e75ce4
wpt-pr: 12109
Automatic update from web-platform-testsAssert correct type for original definition
--
wpt-commits: d8567389060ff683dbff2abff560a3fcbeebc064
wpt-pr: 12144
Automatic update from web-platform-testsAdd objects to ResizeObserver IDL test (#11910)
--
wpt-commits: 83ac30e1574a6209540d16ad6556fcb6f40b4e0d
wpt-pr: 11910
Automatic update from web-platform-tests[WIP] Implemented a prototype H2 Server that can establish HTTP/2.0 connections on port 9000, and serve directories.
* Added event handling for ConnectionTerminated
* Added backwards compatibility with HTTP/1.1 Python handler files.
* Made it so a command line flag is needed to start the H2 server, and it is no longer started by default.
* Refactored compatibility checking when launching HTTP/2.0 server
* Created H1 and H2 handler variants, keeping shared logic in a base class
* Added a `raw_headers` field to the H2Headers object, so that the non-converted keys are exposed
* Added basic multithreading support. Requests now get placed in a thread to finish handling, whilst server listens
for more requests/windows updates.
* Created a ConnectionGuard object for the H2 connection object for thread safety as per jgraham's suggestion
--
Vendored in h2 and its dependencies
--
wpt-commits: 8ccd0cdbb51f89e1c45f16b7843dca1ffca37c91, 0e78a45d9f8ebe9d0f0978d6c2fe59a512e9865b
wpt-pr: 11806
Automatic update from web-platform-tests[idlharness.js] Check idl_test setup func defined (#12143)
Allows the function to be unspecified/null rather than a no-op func.
--
wpt-commits: 67a2edf00ac1e65c6336d3f47638c73c339015d7
wpt-pr: 12143
Automatic update from web-platform-testsSimplify the embedded-enforcement IDL test (#11719)
--
wpt-commits: 5014b841d7841330446ee045d3ced8bf4168900f
wpt-pr: 11719
Automatic update from web-platform-testsEnable LSAN Leak detection in wpt
bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1354232
gecko-commit: e0d106c2112dd6845ca75414258ab74e5ed73d87
gecko-integration-branch: mozilla-inbound
gecko-reviewers: ahal, mccr8
--
Allow wpt manifest files to specify LSAN errors to ignore
This adds a property lsan-allowed to the expectation manifest files
that takes a list of strings. Any entry in the list that matches a
frame in an LSAN stack will cause that stack to be regarded as an
expected failure.
bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1354232
gecko-commit: b8da0ef2695d8bca1c11b44447a71cef5ce5b3fc
gecko-integration-branch: mozilla-inbound
gecko-reviewers: maja_zf
--
Log run-by-dir setting
bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1354232
gecko-commit: 5b9ba77b7316c8ee1d0dac117e33685ebdfe22bc
gecko-integration-branch: mozilla-inbound
gecko-reviewers: maja_zf
--
Support skipping output lines in handlers
bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1354232
gecko-commit: 7c976baa71947b409f92ffd64583440b9a2836b9
gecko-integration-branch: mozilla-inbound
gecko-reviewers: ato
--
Add group_metadata to test group metadata and pass it through to the browser
This initially contains a scope entry which is set to the base directory of
the tests being run. Typically this is /, but with run_by_dir, it's the
path to the current run_by_dir group e.g. /html/semantics/form_elements/
bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1354232
gecko-commit: 07049ac67119a90a0708b0d511562695f725dd9c
gecko-integration-branch: mozilla-inbound
gecko-reviewers: ato
--
Add support for updating LSAN data in wpt-update
LSAN data differs from existing expectation data because the data is
only generated when the browser exits, so the problems reported can
happen at any point in the current session. We use the `scope`
property in the log message to determine the path to a __dir__.ini
file that covers all the tests run in the session, and add the LSAN
exclusion rules to there.
The rules themselves are generated by taking the topmost frame of any
stack that's reported as unexpectedly leaking, and adding that to the
list of permitted frames in the lsan-allowed property. We never remove
entries from this list since intermittents may be present which won't
appear on a specific run. Instead we rely on humans fixing the issues
to also clean up the expectation files.
bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1354232
gecko-commit: 9e8a66385f66f89f8cf2c9a18edf008496fa89fa
gecko-integration-branch: mozilla-inbound
gecko-reviewers: maja_zf
--
Always try to process the leak log whenever we stop firefox
The `stop` method is always called to shutdown firefox, but the
cleanup method is only called at the end of a test run. Therefore we
need all the leak processing stuff ot happen in stop().
bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1354232
gecko-commit: 8cc292a22975583f985da521544b08cf36be6517
gecko-integration-branch: mozilla-inbound
gecko-reviewers: ato
--
Support creating ConditionalValue objects containing a list
bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1354232
gecko-commit: c1ebcf01626ac0e0b23cad5c80ad04ac467fd893
gecko-integration-branch: mozilla-inbound
gecko-reviewers: maja_zf
--
Support a __dir__.ini file in the metadata root
bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1354232
gecko-commit: 0e161374b583a7637db664473e441a1567e82a5b
gecko-integration-branch: mozilla-inbound
gecko-reviewers: maja_zf
--
Fix updating assert count when there's an exising value
In this case we want to take the existing value into account, and update
to 1 more than the new value (in the max-asserts case).
bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1354232
gecko-commit: 0f2a7154454ceec763bd64597ad9e3155c8d091c
gecko-integration-branch: mozilla-inbound
gecko-reviewers: maja_zf
--
Refactor data storage in metadata.py
Previously we were holding a map of test id -> test and test ->
expectation data. But this is an unnecessary layer of indirection, and
it works perfectly well to map test id to the expectation data
directly. This makes the code simpler and may also help make the
update a little faster.
bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1354232
gecko-commit: 6bf4a20193b801d342ff662b5a9712e516561d9e
gecko-integration-branch: mozilla-inbound
gecko-reviewers: maja_zf
--
Fix, enable, and add to, the manifest update tests
Refactor the tests to make them work with pytest directly rather than
also depending on unittest. Fix the helper functions to work with the
current state of metadata.py. Add some tests for update of assertion
count and lsan data.
bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1354232
gecko-commit: 5028820efd9ed3d1dbcb9bde5cbc235414a8d23c
gecko-integration-branch: mozilla-inbound
gecko-reviewers: maja_zf
--
Don't store the result of update_expected
The needs_human feature never worked well and is unused.
bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1354232
gecko-commit: 004b079b76d06c3e9d74210700b28994cdeff886
gecko-integration-branch: mozilla-inbound
gecko-reviewers: maja_zf
--
Chunk by dir more for wpt on asan
This means that when we run these tests, the LSAN exceptions will have
the minimum possible scope.
bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1354232
gecko-commit: a7dec081ead2ac3b5d20b99b2bb177719358e328
gecko-integration-branch: mozilla-inbound
gecko-reviewers: maja_zf
--
Fixup flake8 failures
--
Fix flake8 issues in master on servodriver
--
wpt-commits: 9a57710275e1ac52d4c3d3426b370e3f31c46856, 49193c2e02fc20fc1d28e5957d4f3a6fd52adfd3, 429d1b8353e0e1b601bd34ba98fdff290780b127, aa9bdbf0639326900d232f155449e7950adc0649, 91803e3a25afd8e0c201bc57cd05fffd5d543551, df7e6cdf297c06a05b5a116f51fb203cda295809, d8aaec5ffebb93db1b54ccdafb0d7a2897428427, 4d21dcbb1bd9612715ac9ed55c3ec271b3c4e1ca, aa3a405237c3d45187f76906367161a7e9a486a0, 68c8996844a6774aadfd14da4c02c71bb5d9d342, d4b2146217d338e278e24bb3bc705871b50e9c7e, f814a0f1c23cb76e36b6732165c92fa327d86f40, 5782d6704b66adbcce7398911a74a4abdf323ef7, dcfcadb2c6892a187de6f0be7c42eed09d91fe90, 17796c6272e4fe3d1bba24fdfe261572b1ad757a, 654133c23efb269585009818b6f4547d130cb564
wpt-pr: 12073
Automatic update from web-platform-testsClean up the service-workers IDL test (#11960)
--
wpt-commits: 0eaf7a15b526a10f512654cbe9a7fb88de98f8ba
wpt-pr: 11960
Automatic update from web-platform-testsAdd a test for Gecko bug 1472169. (#12124)
It's not clear that we want the fix over there given the performance
implications, but landing the test is still worth it.
--
wpt-commits: 3f9178031eec5374c9a7d5709a7e11ba4a1955ed
wpt-pr: 12124
Automatic update from web-platform-testsRevert "[css-text] A leading white-space should break before handling overflow"
This reverts commit 6ea2a2e7f3ef01e0c98424ce272a732ade92ad1a.
Reason for revert: <INSERT REASONING HERE>
Original change's description:
> [css-text] A leading white-space should break before handling overflow
>
> Leading white-spaces are indeed breaking opportunities that should
> prevent, if there are no other css properties forcing it, breaking text
> in the middle of a word when honoring the word-wrap/overflow-wrap CSS
> property.
>
> We are doing so if the leading white-space sequence is longer than 1
> character, but when we have a single leading white-space, we are missing
> that breaking opportunity and we may lead to cases, like the one
> described in the bug.
>
> However, this breaking opportunity should be considered together
> with other provided by the word-break CSS property (eg, break-word or
> break-all).
>
> There is a discussion [1] in the CSS WG github about this issue, which
> provides an interoperability analysis of a few cases where a single
> leading white-space character may produce different results, depending
> on the browser and the combination of line-breaking properties.
>
> [1] https://github.com/w3c/csswg-drafts/issues/2907
>
> Bug: 854624
> Change-Id: I49ec8282e899a32990662c104b48cab04057b909
> Reviewed-on: https://chromium-review.googlesource.com/1130515
> Commit-Queue: Javier Fernandez <jfernandez@igalia.com>
> Reviewed-by: Koji Ishii <kojii@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#575596}
TBR=jfernandez@igalia.com,kojii@chromium.org
# Not skipping CQ checks because original CL landed > 1 day ago.
Bug: 854624
Change-Id: I9ee4cd370dd92b74f9fdc4f42d16638253dd2dee
Reviewed-on: https://chromium-review.googlesource.com/1146360
Reviewed-by: Javier Fernandez <jfernandez@igalia.com>
Commit-Queue: Javier Fernandez <jfernandez@igalia.com>
Cr-Commit-Position: refs/heads/master@{#577096}
--
wpt-commits: 040f31fa8f6250c54160d0257c6b411ccac59f61
wpt-pr: 12138
