CLOBBER
author Mike Hommey <mh+mozilla@glandium.org>
Mon, 30 Nov 2015 17:43:06 +0900
changeset 308989 e03b93cbb64d4996a9f170d76a69801b9a708d84
parent 307654 a53407e2b844002554266f2029f25f1bbd9bedca
child 310437 e2031358e2a6d6d686b7a6b592d07cfb874bacae
permissions -rw-r--r--
Bug 1229233 - Add a (incomplete) end-to-end build test. r=gps We have many unit tests in the tree for some small parts of the build system pipeline, but we don't have anything that resembles an end to end test, and we kind of rely on the resulting Firefox not being broken by our changes. With the Faster make backend growing, I want to ensure it produces the same thing as the recursive make backend, at least for the parts it supports. This adds some kind of test that allows to check that.

# 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 1210165 - Update ICU to release 56.1.
Bug 966038 - Updating ICU doesn't properly notify the Mozilla build system, necessitating a clobber.