Page History
- 2015-Oct-02 14:17 johnkn
- 2015-Sep-30 14:32 johnkn
- 2015-Sep-29 17:43 johnkn
- 2015-Mar-30 13:13 bt
- 2014-Oct-16 13:43 adesmet
- 2014-Oct-08 17:42 adesmet
- 2014-Jul-24 10:57 bt
- 2014-Jul-24 10:54 bt
- 2014-May-09 14:43 gthain
- 2014-Mar-31 14:14 adesmet
- 2014-Mar-31 14:00 adesmet
- 2013-Nov-19 11:32 adesmet
- 2013-Nov-14 14:19 adesmet
- 2013-Oct-31 08:59 bt
- 2013-Sep-11 14:16 bt
- 2013-Sep-11 14:13 bt
- 2013-May-16 13:48 bbockelm
- 2013-Apr-15 11:44 bt
- 2013-Apr-15 11:26 bt
- 2013-Apr-15 10:18 bt
- 2013-Apr-15 10:17 bt
- 2013-Apr-15 10:12 bt
- 2012-Nov-13 16:48 adesmet
- 2012-Oct-16 15:28 nwp
- 2012-Sep-07 14:19 adesmet
- 2012-Sep-07 11:22 adesmet
- 2012-Sep-07 11:22 adesmet
- 2012-May-24 11:24 kronenfe
- 2012-May-24 11:07 kronenfe
- 2012-May-24 11:06 kronenfe
- 2012-May-24 11:06 kronenfe
- 2012-May-24 11:05 kronenfe
- 2011-Aug-11 15:33 adesmet
- 2011-Mar-17 15:30 adesmet
- 2011-Mar-17 14:16 adesmet
- 2011-Mar-17 14:03 adesmet
General
batch_test.pl is the means by which the test suite is run. It can be told to start up its own personal Condor and use that for testing. The tests ran by batch_test.pl may also start their own personal Condors.
First, make sure the tests are built:
$ make tests
Then, invoke batch_test.pl. We tell batch test to start up its own personal condors and clean up everything when it is done. We don't ask it to run tests in parallel since there likely are race conditions in the tests over that behavior.
$ cd src/condor_scripts $ ./batch_test.pl -b -c
Running the tests again
Running the test suite leaves files and directories in the src/condor_tests directory that prevent the tests from running again. To solve this:
$ rm -fr ../condor_tests/TestingPersonalCondor
Warnings, Problems, and Workarounds
See #1124 for tickets associated with improving tests.
- You can't currently (2011-03-17) do out-of-source tests. You'll need to build and test inside of your repository.
- Corollary: this will make will your repository with lots of new files Git will complain about. Solution: Make a copy of your repository before doing tests.
- Several tests do "chmod -R 777 ." on the testing directory. This needs to be fixed as it's insecure and it angers Git (which sees the permission change as something to be committed). This needs to be fixed (#1978). In the meanwhile: Make a copy of your repository before doing tests.
- Several tests rewrite files in place, making them appear like they have changes that you should check in. Checking them in would be very wrong. This needs to be fixed (#1983). IN the meanwhile: Make a copy of your repository before doing tests.
- You might be able to fix the permissions with:
git diff | grep diff | awk '{print $3}' | sed -e 's@a/src/condor_tests/@@' | xargs chmod 644
- You might be able to fix the permissions with:
- Parallel tests are unlikely to work. A number of tests depend on the output from other tests. Furthermore, some tests assume no competition and may reuse files or directories.
- Re-running tests is unlikely to work. Tests leave a lot of garbage behind that causes problems when they run again. Solution: x_makeclean.pl or "make resubmit" might clean things up enough. (#1153 is unfinished work designed to help with this.)