CLOBBER
author Ryan VanderMeulen <ryanvm@gmail.com>
Mon, 20 May 2013 14:10:23 -0400
changeset 143932 22211594d2a739b5072bbf629a9c417c1ced8fed
parent 143869 8aef76919ec0e1308d51b77b68f76df75f865131
child 143984 0931f7400cf2af6e6ee742b6beb17f92069755f8
permissions -rw-r--r--
Bug 855762 - Disable another test on Android due to high failure rate.

# 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/
#
Landing bug 865806

Alternative to clobber is to run ./config.status from the objdir and to
touch the CLOBBER file in the objdir.