CLOBBER
author Ryo Kato <ryo_kato@hashedhyphen.com>
Sun, 03 Apr 2016 16:20:20 +0900
changeset 292524 afdcc508d7644bbe87de12f4435cd67538e225c8
parent 292376 3ce37297f52f339351935fdb6166d83a9cd0cd27
child 293744 7bffe558f364bea04f7e3eea847cc05e12d3e0ab
permissions -rw-r--r--
Bug 1255682 - Remove unnecessary t.step_func() from a chrome test r=hiro In promise chains, we don't have to use t.step_func. However, when there are callbacks in promise chains, assertions in the callbacks need wrapped in either t.step or t.step_func. If we use t.step_func, a variable scope might be divided. This can be a problem when an assertion uses local-scope variable (e.g. the callback in MutationObserver uses an assertion which take `changedAnimation`). Therefore, t.step is helpful in this case. (There no t.step_func we should remove in web-platform tests.) MozReview-Commit-ID: IiSizgCQjpG

# 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 1186060 - Switch Windows compiler from VS2013 to VS2015