Menu
▾
▴
#227 Inconsistent number of tests created
new
nobody
None
normal
minor
havenottried
none
Linux
Intel
Test Harness
2014-06-08
2014-06-03
No
When running the testHarness in the vagrant machines on the exactly source trees 2 Linux-machines report 207 tests the other 208
The missing test is multiSolver/multiSolverDemo/teeFitting2d/parTeeFitting2d
---- steps_to_reproduce ----
Must check tomorrow which one is the one with 208. The three used vagrant-boxes were
- trusty (Ubuntu 14.04)
- Centos 6.5
- OpenSUSE
Sorry. Abusing this ticket to test the CDash-field (enforce at least "none" in it)
CentOS is the Distro that reports 208 tests. All others 207 (Mac OS X reports 207 too)
Asked in #226 whether the tutorial case could be moved up. This only fixes the Symptoms but I guess it would be good enough
I'm confused. It is OpenSUSE12 in the vagrant boxes that reports 208 tests http://openfoam-extend.sourceforge.net/CDash/buildSummary.php?buildid=673 Contrary to previous reports Centos reports 207 http://openfoam-extend.sourceforge.net/CDash/buildSummary.php?buildid=670 BUT Centos not in the vagrant box reports 208 http://openfoam-extend.sourceforge.net/CDash/buildSummary.php?buildid=655
This could be a cmake/ctest related problem. Could you check your version of cmake from the configuration where you find a missing test case?
When the test harness is preparing its suite of test cases to run, it will do the following:
1: Make a fresh local copy of the $FOAM_TUTORIAL directory available with your current foam-extend release. So for instance, make sure the process running your testHarness has read permission to all your tutorial directories. The copy of the whole tutorial tree will be made by a ctest instruction.
2: Find all test cases with a missing Allrun file, and add a default one if none are present.
If the test case does not have an Allrun file once this step #2 is done, then the test case will not be run by the test harness, hence no report on the CDash server about this little guy. This search-and-add operation will be made by a bash script called "addMissingAllrunFileToTutorial.sh"
You might want to run the script : ./Allrun_CMakeOnly which is only taking care of the preparation part the test harness. This script will not run any of the test harness cases, just prepare them, so this should be fairly quick.
Once this script had done its job, you can then explore the resulting suite of test cases, and maybe find any missing pieces that the test harness scripts failed to do properly.
For any test case to run, you will need an Allrun file. Either the original one already provided by the tutorial, or a rather simple one provided by the test harness.
And the default Allrun script is fairly simple: blockMesh + running the solver specified by the "application" string in your case's controlDict. Nothing more.
If the specified application does not exist, your case will still run, but with an error message like "xxx: command not found". And this situation will be reported on the CDash server, so no missing report even for that case.
Will verify this later this week (have to downgrade the installations because) but it seems that the versions I used (and I don't see a pattern) are:
- Centos non-vagrant: 2.6-patch 4 (got 208 cases)
- Centos vagrant: 2.8.12 (got 207)
- OpenSUSE: 2.8.11.2 (got 207)
- Mac 2.8.12.2 (got 207)
So maybe it is CMake 2.6