Page History
- 2022-Jul-27 13:02 johnkn
- 2017-Mar-28 09:15 johnkn
- 2017-Mar-28 09:14 johnkn
- 2016-Mar-18 15:05 johnkn
- 2016-Mar-17 13:16 johnkn
- 2016-Mar-17 11:35 johnkn
- 2016-Mar-17 10:43 johnkn
- 2016-Mar-16 12:14 johnkn
- 2016-Mar-16 12:08 johnkn
- 2016-Mar-16 11:52 johnkn
- 2016-Mar-15 17:17 johnkn
- 2016-Mar-15 16:36 johnkn
- 2015-Jul-30 15:25 bt
- 2015-Jul-30 15:22 bt
- 2015-Jul-30 15:21 bt
- 2015-Jul-30 14:32 bt
- 2015-Jul-30 14:27 bt
- 2015-Jul-30 13:50 bt
- 2015-Jul-30 13:48 bt
- 2015-Jul-30 13:45 bt
- 2015-Jul-30 11:56 bt
- 2015-Jul-30 11:25 bt
- 2015-Jul-30 10:55 bt
- 2015-Jul-30 10:33 bt
- 2015-Jul-30 10:26 bt
- 2015-Jul-30 10:22 bt
- 2013-Sep-20 13:29 bt
- 2013-Sep-20 13:21 bt
- 2013-Sep-20 12:53 bt
- 2013-Sep-20 12:19 bt
- 2013-Sep-06 14:31 bt
- 2013-Apr-15 11:44 bt
- 2013-Apr-15 11:12 bt
- 2012-Nov-13 16:48 adesmet
- 2009-Mar-05 16:53 burnett
- 2009-Feb-05 17:58 burnett
- 2009-Jan-28 12:08 burnett
- 2009-Jan-27 09:32 burnett
- 2009-Jan-16 18:26 burnett
- 2009-Jan-14 15:42 burnett
- 2009-Jan-14 11:52 burnett
- 2009-Jan-13 15:01 burnett
Requirements
- Install Cygwin + Cygwin Perl module
- Install Active-State Perl
- Install HTCondor
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
CONDOR_HOST = 127.0.0.1 NETWORK_INTERFACE = 127.0.0.1 DAEMON_LIST = MASTER STARTD KBDD COLLECTOR NEGOTIATOR SCHEDD
Testing
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
From a Cygwin command-line type:
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
Or, to run a single test:
./batch_test.pl -d . -b -t cmd_q_shows-name
Where cmd_q_shows-name
can be any of the tests in the test suite. As a final note, if you are planning on running the tests several times, you will need to delete the TestingPersonalCondor
directory between test runs:
rm -rf TestingPersonalCondor
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.