testsuite: Remove build_farm testsuites

[kai/samba-autobuild/.git] / source4 / selftest / win / README

diff --git a/source4/selftest/win/README b/source4/selftest/win/README
index fc934385c4d849745aa95fc3963efb084d684e7d..f6e716c8da029dfb9d2c48a31d1a006396efe8c8 100644 (file)
--- a/source4/selftest/win/README
+++ b/source4/selftest/win/README
@@ -70,52 +70,3 @@ remotely administered with telnet. Specifically, this will allow us to use
 'make wintest' in Samba 4 to perform smbtorture tests against a Windows host,
 and perform tests from a Windows client to a Samba server.
 
-INTEGRATING WITH THE BUILD FARM
-
-Follow the standard steps to add a host to the build farm. The major
-difference is that we will need to run these tests as root. To run the
-Windows tests in the build farm, a .fns file will need to be created for
-your new host that exports a WINTESTCONF environment variable pointing to a
-config file used by 'make wintest'. An example of this config file can be
-found at source/selftest/win/test_win.conf in the Samba 4 source tree. 
-
-I've also included the bnhtest.fns file that I'm using for my build farm host
-below, as an example. It was modified from generic.fns.
-
-action_test_windows() {
-        do_make wintest
-        w_status=$?
-        echo "WINTEST STATUS: $w_status"
-        return $w_status;
-}
-
-per_run_hook
-
-system=`uname`
-
-export WINTESTCONF="/home/build/win/test_win.conf"
-
-for compiler in gcc cc icc; do
-
-  # arrgh, "which" gives no err code on solaris
-  path=`which $compiler`
-  if [ -x "$path" ]; then
-
-    if $compiler -v 2>&1 | grep gcc.version > /dev/null; then
-       isgcc=1
-       CFLAGS="-Wall"
-       export CFLAGS
-    else
-       CFLAGS=""
-       export CFLAGS
-       isgcc=0
-    fi
-    if [ $compiler = gcc -o $isgcc = 0 ]; then
-
-      # only attempt samba4 if we have perl
-      if which perl > /dev/null; then
-        test_tree samba4 source $compiler configure build install test_windows test
-      fi
-    fi
-  fi
-done