CLOBBER
author Andreea Pavel <apavel@mozilla.com>
Thu, 26 Apr 2018 10:45:11 +0300
changeset 471776 42c89029f1ad0f7b8ac9835d9db659bffc713419
parent 468936 f041c724fb809d3c927000e38bf67034d3a3930e
child 471846 064c3804de2e967753bcba437523892da918f67a
child 472914 3914937893dee9b5370128bddfa41d4f3627d8db
permissions -rw-r--r--
Backed out changeset fb836a045f20 (bug 1438375) for browser chrome failures at browser/components/preferences/in-content/tests/browser_extension_controlled.js a=backout

# 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 1453317 - Update VS2017 used for builds in automation to version 15.6.6.