Remove Skia's forked buildbot code

configs/chromium/slave/Makefile

Index: configs/chromium/slave/Makefile
diff --git a/configs/chromium/slave/Makefile b/configs/chromium/slave/Makefile
deleted file mode 100644
index 3ad891fa13839c5adc1c4f6575133e0b1babb33c..0000000000000000000000000000000000000000
--- a/configs/chromium/slave/Makefile
+++ /dev/null
@@ -1,61 +0,0 @@
-# -*- makefile -*-
-
-# This is a simple makefile which lives in a buildmaster/buildslave
-# directory (next to the buildbot.tac file). It allows you to start/stop the
-# master or slave by doing 'make start' or 'make stop'.
-
-# The 'reconfig' target will tell a buildmaster to reload its config file.
-
-# Note that a relative PYTHONPATH entry is relative to the current directory.
-
-# On the Mac, the buildbot is started via the launchd mechanism as a
-# LaunchAgent to give the slave a proper Mac UI environment for tests.  In
-# order for this to work, the plist must be present and loaded by launchd, and
-# the user must be logged in to the UI.  The plist is loaded by launchd at user
-# login (and the job may have been initially started at that time too).  Our
-# Mac build slaves are all set up this way, and have auto-login enabled, so
-# "make start" should just work and do the right thing.
-#
-# When using launchd to start the job, it also needs to be used to stop the
-# job.  Otherwise, launchd might try to restart the job when stopped manually
-# by SIGTERM.  Using SIGHUP for reconfig is safe with launchd.
-#
-# Because it's possible to have more than one slave on a machine (for testing),
-# this tests to make sure that the slave is in the known slave location,
-# /b/slave, which is what the LaunchAgent operates on.
-USE_LAUNCHD := \
-  $(shell [ -f ~/Library/LaunchAgents/org.chromium.buildbot.slave.plist ] && \
-          [ "$$(pwd -P)" = "/b/build/slave" ] && \
-          echo 1)
-
-TOPLEVEL_DIR := $(shell pwd)/../../../third_party/chromium_buildbot
-export PYTHONPATH=$(TOPLEVEL_DIR)/third_party/buildbot_7_12:$(TOPLEVEL_DIR)/third_party/twisted_8_1
-
-# Note that initscripts and make can conspire to leave child processes with
-# an unlimited maximum stack size. This causes the Linux kernel to use a
-# strange VM layout.
-# We therefore explicitly set a (typical) stack limit.
-start:
-ifneq ($(USE_LAUNCHD),1)
-	sh -c 'ulimit -s 8192; python run_slave.py --no_save -y buildbot.tac'
-else
-	launchctl start org.chromium.buildbot.slave
-endif
-
-stop:
-ifneq ($(USE_LAUNCHD),1)
-	if `test -f twistd.pid`; then kill `cat twistd.pid`; fi;
-else
-	launchctl stop org.chromium.buildbot.slave
-endif
-
-reconfig:
-	kill -HUP `cat twistd.pid`
-
-log:
-	tail -F twistd.log
-
-wait:
-	while `test -f twistd.pid`; do sleep 1; done;
-
-restart: stop wait start log