{section: Requirements}
-*: Cygwin + Cygwin Perl module
-*: Active-State Perl
+*: Install Cygwin + Cygwin Perl module
+*: Install Active-State Perl
+*: Install HTCondor
+
+
+{section: Preparing for testing}
+
+The easiest way to get an ititial Windows HTCondor test environment
+is to install the HTCondor msi. Take all the defaults and when you get
+to where jobs run, allow them to run unimpeeded on the current system.
+(After you have a test machine set up, you can replace the binaries with ones
+from the zip file release for HTCondor)
+
+You will find it helpful to place these 3 lines in c:condor/condor_config.local
+
+{code}
+CONDOR_HOST = 127.0.0.1
+NETWORK_INTERFACE = 127.0.0.1
+DAEMON_LIST = MASTER STARTD KBDD COLLECTOR NEGOTIATOR SCHEDD
+{endcode}
{section: Testing}
+{code}
+Add to the system PATH environment variable the location of the HTCondor binaries
+Secure the HTCondor source tar ball and extract it
+Bring down to a testing location of your choice:
+ condor_examples
+ condor_scripts
+ condor_tests
+Copy *.pm and batch_test.pl from condor_scripts to condor_tests
+{endcode}
+
From a Cygwin command-line type:
- export NMI_PLATFORM=x86_winnt_5.1
- export PATH=$PATH:/cygdrive/c/condor/bin
- cd /cygdrive/c
- mkdir nmi_tests
- pushd /cygdrive/c/workspace/source/src
- cp -r condor_{examples,scripts,tests} /cygdrive/c/nmi_tests
- popd
- cd nmi_tests/condor_tests
- cp ../condor_scripts/*.pm ../condor_scripts/batch_test.pl .
+{code}
+cd c:/condor
+chmod go+rX bin
+cd bin
+chmod go+rX *
+cd (into condor_tests, where ever you placed it)
+./batch_test.pl -d . -b
+{endcode}
-Then, to run all the tests (optionally using test parallelization feature [-e]):
- ./batch_test.pl -d . -b -e 10
Or, to run a single test:
@@ -29,8 +54,5 @@
rm -rf TestingPersonalCondor
-Finally, if you just want a personal HTCondor up and running quickly, use:
-
- ./batch_test.pl -p
That's about as simple as it gets; although it is possible to save exporting the =NMI_PLATFORM= and =PATH= each time. This can be accomplished by adding them to the environment in a persistent manner; either by cygwin startup scripts or changing the Windows environment. The latter will require a new instance of the cygwin terminal for the variables to be present.
