Revision 4f06a45252465792447f80b6559b17c4c4e9712c authored by Daniel Vogelheim on 10 April 2018, 13:07:39 UTC, committed by Chromium WPT Sync on 10 April 2018, 13:07:39 UTC
Allow control of the deprecation via runtime enabled features, with a first
step for logging a warning to the console, and the second step to block it
outright.
Intent: https://groups.google.com/a/chromium.org/d/msg/blink-dev/35t5cJQ3J_Q/FH45dl0vAwAJ
Change-Id: I1be1001cbbef152458119b1516750bb4f1d1e4de
Reviewed-on: https://chromium-review.googlesource.com/975611
Commit-Queue: Daniel Vogelheim <vogelheim@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Cr-Commit-Position: refs/heads/master@{#549495}
1 parent 069680c
check_stability.ini
[file detection]
skip_tests: conformance-checkers docs tools
# The vast majority of tests rely on files located within the `resources`
# directory. Because of this, modifications to that directory's contents have
# the potential to introduce instability in a large number of tests.
# Exhaustively validating such changes is highly resource intensive
# (particularly in terms of execution time), making it impractical in most
# cases.
ignore_changes: resources
results_url: https://pulls.web-platform-tests.org/api/stability
Computing file changes ...
