Debugging with the --include_only command line parameter

There are times when running the full suite of Intel® Cluster Checker test modules is not desired. When debugging a known issue or just wanting to test a specific component in the cluster, using the --include_only command line parameter will save time by focusing in on the relevant issue.

Once you know the name of the desired module to execute, it is simple to launch the tool to execute up to that module and stop. For instance, if it is desired to run just the intel_mpi_rt module, the following command line can be used:

cluster-check config.xml --include_only mflops_intel_mkl

This instructs Intel® Cluster Checker to run the test module specified and include only any other modules that are upstream in the dependency list or have been explicitly included in the configuration file.

Executing the above command will then only include the following tests to be run:

Exclusively including modules (at user request):
'mflops_intel_mkl'

Including modules (to meet dependency requirements):
'genuine_intel'
'mount_proc'
'ping'
'sh'
'ssh'
'tmp'


Now assume for this example that config.xml contains the following tag to explicitly include a module:

<include_module>openib</include_module>

Executing the same command above with this tag in the configuration file will cause the explicitly included module to execute as well:

Exclusively including modules (at user request):
'mflops_intel_mkl'

Including modules (at user request):
'openib'

Including modules (to meet dependency requirements):
'genuine_intel'
'mount_proc'
'ping'
'sh'
'ssh'
'tmp'

Notice the inclusion of the openib test module even though it is not in the dependency list of the mflops_intel_mkl test module. If the configuration file contains many tags that are explicitly included, it may be beneficial to create a temporary configuration file and remove those items. This can save time running specific test modules when debugging or checking a single component of the cluster.

Using the --include_only option is an effective debugging tool that saves time troubleshooting and resolving minor issues since full Intel® Cluster Checker runs are not needed to test a single component. Once an individual issue is resolved and the corresponding test module is passing, then the full test suite can be run to verify the cluster is compliant and running correctly.
For more complete information about compiler optimizations, see our Optimization Notice.