CLOBBER
author Jean-Yves Avenard <jyavenard@mozilla.com>
Tue, 14 Oct 2014 12:49:32 +1100
changeset 225718 9be2b1620955138f7fae96892f85f345c36728f3
parent 224572 aed50d3edf33828b45f84e99c52a70b56b630e4a
child 228134 e1d819297fe4600590479e21c31188a236a8dd55
permissions -rw-r--r--
Bug 1079621 - Return error instead of asserting. r=kinetik, a=lmandel From c2a87a986f6d0ed699ab0fbf5687d8aa5fea8ff0 Mon Sep 17 00:00:00 2001 NS_ASSERTION is debug-only, and fails silently in continuous integration. Better to return an error here, since failure could result in a crash later.

# 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.

Merge day clobber