Page History
Testing a HTCondor workspace in NMI
Before you start, make sure that you have an account on submit-3.batlab.org.
From your usual machine, you want to create a temporary workspace directory on submit-3, and then archive a commit of your git clone into that directory. In this directory, we call the directory 'workspace' but it can be anything.
ssh submit-3.batlab.org mkdir workspace cd <to top of clone, usually CONDOR_SRC> git write-tree
On Linux the command is
git archive <hash created by git write-tree> | ssh submit-3.batlab.org cd workspace '&&' tar xf -
git archive <hash created by git write-tree> | ssh submit-3.batlab.org cd USERNAME@submit-3.batlab.org cd workspace ; tar xf -
So far, this is the same as submitting a workspace build.
Next, go to http://submit-3.batlab.org/results/continuous.php and choose a recent completed build to run tests against. Then run the following commands, substituting the id of the build for <runid>
cd workspace cd nmi_tools ./condor_nmi_submit --test --buildid=<runid> --workspace=../ --platforms=all --notify-fail-only --desc="A Description" --ignore-missing-platforms --test-sources-from-workspace
You can go to http://submit-3.batlab.org/results/workspace_tests.php in a few seconds and see your test run show up.
It will also be visible on the bottom of the details page for the build, which you can find by substituting the build id that you chose for <runid>
in this link.
http://submit-3.batlab.org/results/run-details.php?runid=<runid>
You can pass additional arguments to condor_nmi_submit to alter the test configuration
--append-config-dir=<dir>
Copy<dir>/testconfigappend
into the condor_tests directory before running the tests. The test glue will then append this file to the base condor_config produced by condor_install, and before running any of the tests. Use this to make a global config change, such as turning on IPV6