CLOBBER
author Emilio Cobos Álvarez <emilio@crisal.io>
Wed, 08 May 2019 12:44:46 +0000
changeset 473059 eee17e1b043502d063b1d609bd98750e91c1bc00
parent 467951 d10b57a89a73db612a1856bee1975e7cdcbe0e7b
child 474505 0a9b9344eb3507714ac3c30485d71bb8387ff3c2
permissions -rw-r--r--
Bug 1538101 - Don't report errors for properties for which we've parsed another value in the same declaration block. r=jdm I thought a bit about how to test it and it's not particularly great. test_css_parse_error_smoketest.html is great to assert that something _gets_ reported, but not that it doesn't :) Differential Revision: https://phabricator.services.mozilla.com/D30201

# To trigger a clobber replace ALL of the textual description below,
# giving a bug number and a one line description of why a clobber is
# required. Modifying this file will make configure check that a
# clobber has been performed before the build can continue.
#
# MERGE NOTE: When merging two branches that require a CLOBBER, you should
#             merge both CLOBBER descriptions, to ensure that users on
#             both branches correctly see the clobber warning.
#
#                  O   <-- Users coming from both parents need to Clobber
#               /     \
#          O               O
#          |               |
#          O <-- Clobber   O  <-- Clobber
#
# Note: The description below will be part of the error message shown to users.
#
# Modifying this file will now automatically clobber the buildbot machines \o/
#

# Are you updating CLOBBER because you think it's needed for your WebIDL
# changes to stick? As of bug 928195, this shouldn't be necessary! Please
# don't change CLOBBER for WebIDL changes any more.

Bug 1533481 - Update to ICU 64 requires clobber