CLOBBER
author Jean-Yves Avenard <jyavenard@mozilla.com>
Tue, 20 Sep 2016 15:51:54 +1000
changeset 355719 7a1355cb3354edc65fe6072bd51984276a5f5cd2
parent 355659 5dddbefdf759f09b1411f33fa0920835b919fc81
child 357774 11e6496ab698a88c0e08b8141485380e0eeef364
permissions -rw-r--r--
Bug 1303673 - Part 2: Change error code to OOM. r=cpearce, a=gchang Only time this error can occur is if we failed to allocate memory. MozReview-Commit-ID: A37SQnraC54

# 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