{subsection: Testing a Previous Condor Build}
-Somebody will need to write this up. It should have a nice explanation of all the different condor_nmi_submit options:
+If the build you want to test was a workspace build, you can submit the tests using the same workspace. Run this from the =nmi_tools= directory of your workspace:
{code}
---buildid=string <Build RunId to test>
---test-src=string <Custom source tarball for building tests with>
---test-args=string <Arguments to select what tests to declare>
---test-timeout=int <timeout in minutes for each test task (default is 20)>
---platforms=all <will query DB for all platforms in the given buildid>
+./condor_nmi_submit --test --buildid=209633 --git --platforms=all \
+--workspace=.. --submit-xtests
{endcode}
+You can restrict the set of platforms tested by giving a comma-separated list for the =--platforms= option. If you don't want any cross-platform tests, you can use =--nosubmit-xtests=.
+
+{section: The following is old documentation that needs to be updated or removed}
+
{subsection: Using a Workspace Directory to Test a Previous Condor Build}
For this scenario, my job_core_max-local-running tests were producing false negatives on random platforms in the nightly build. I wanted to make a fix to the test files and then test my changes against the previous night's build. These instructions will allow you to do that without having to commit any of your changes to CVS.
