Page History

Turn Off History

***Clarified / Updated 7/30/15 bt***

Requirements

in CS to have networking work the best, my condor_config looks like this: 

use ROLE : CentralManager Execute Submit
CONDOR_HOST = bt-laptop.cs.wisc.edu
#use ROLE : Personal
#CONDOR_HOST = 127.0.0.1
COLLECTOR_HOST = $(CONDOR_HOST):0

# use host based security, modified to allow the other crane to join the pool.
use SECURITY : HOST_BASED
if 1
MY_CS_SUBNET = 128.105.136
BT_IP = $(MY_CS_SUBNET).32
ALLOW_READ = $(CONDOR_HOST) $(BT_IP)/8 $(IP_ADDRESS)
ALLOW_ADMINISTRATOR = $(ALLOW_ADMINISTRATOR) $(BT_IP)
ALLOW_WRITE = $(ALLOW_ADMINISTRATOR)
endif

On my laptop in CS my condor_config.local looks like this: 

FULL_HOSTNAME = bt-laptop.cs.wisc.edu
MASTER_NEW_BINARY_RESTART   = PEACEFUL
RunBenchmarks = 0
NUM_CPUS = 12
MASTER_DEBUG = D_CAT D_FULLDEBUG

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)

Testing needs

On my laptop I have the MSI installed to c:\condor with my test location assembled in c:\condor_tests and condor_examples in c:\condor_examples.

There are four things needed for testing on windows that need to be assembled

  1. built tests
  2. all sources for src/condor_tests and src/condor_examples
  3. Condor.PM, CondorUtils.pm, CondorTest.pm, CondorPersonal.pm and batch_tests.pl from src/condor_scripts
  4. placement choices: The directory condor_examples needs to be in same folder as condor_tests.
  5. If the condor perl modules are not in a well known system location place them in your selected test location. 

Add to the system PATH environment variable the location of the HTCondor binaries

Set Up Option 1

  1. Secure the HTCondor source tar ball and extract it if you do not have a git clone
  2. Bring down to a testing location of your choice as mentioned above condor_examples condor_scripts condor_tests
  3. Copy *.pm and batch_test.pl from condor_scripts to your condor testing location
  4. Copy all of the built tests contents to your selected condor testing location
  5. Place condor_examples in the same folder as your selected testing location {endcode}

Testing 2

  1. Another way to do this is to first have a fully working HTCondor on a PC from the msi.

  2. Have cygwin and condor in your windows PATH envrionment variable. Mine has c:\bin\;C:\condor\bin\ added
  3. Download a valid windows build result tar ball which contains release rpm, test programs compiled for windows and all needed perl modules and scripts.
  4. Stop HTCondor. First do condor_off -master in a cygwin window and then using task manager kill the keyboard daemon.
  5. Take the release zip file and extract it on top of your HTCondor install after making sure all of HTCondor is completely stopped
  6. Pick a location for testing( I have /condor /condor_tests and /condor_examples.
  7. Place condor_tests from build result tar to desired location
  8. Place condor_examples next to it
  9. If you want to stress test, edit condor_config.local in /condor to have NUM_CPUS = somegreaternumberthencores
  10. Restart your system to get HTCondor running with new binaries.
  11. open a cygwin windows and test basic commands like codnor_q and condor_status. 1. Open a cygwin shell and go to condor_tests
  12. Enter "./batch_tests.pl -b -d .
  13. wait

Results 

249 successful, 34 failed

Additionally the file failed_tests will contain the list of tests which had a non-zero return code meaning they failed. The file successful_tests will list the passing tests which had a return value of zero

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.

If you wish to stress test:

./batch_test.pl -b -d . -e 6 { run 6 tests at a time }