These are results from the (now working again) nightly build tests, in particular on Mac OS X:
Summary for configuration einsteintoolkit
Total available tests -> 80 Unrunnable tests -> 54 Runnable tests -> 26 Total number of thorns -> 105 Number of tested thorns -> 7 Number of tests passed -> 5 Number passed only to set tolerance -> 3 Number failed -> 21
"Unrunnable" means likely that a necessary thorn is not present, such as ADM. "Failed" test, well, fail.
So our success rate is 6%.
-erik
Is the number of tested thorns below actually useful? I assume this is the number of thorns that contained testsuites rather than the number of thorns that were activated in any of the testsuites?
On Apr 13, 2010, at 12:33 AM, Erik Schnetter wrote:
These are results from the (now working again) nightly build tests, in particular on Mac OS X:
Summary for configuration einsteintoolkit
Total available tests -> 80 Unrunnable tests -> 54 Runnable tests -> 26 Total number of thorns -> 105 Number of tested thorns -> 7 Number of tests passed -> 5 Number passed only to set tolerance -> 3 Number failed -> 21"Unrunnable" means likely that a necessary thorn is not present, such as ADM. "Failed" test, well, fail.
So our success rate is 6%.
-erik
-- Erik Schnetter schnetter@cct.lsu.edu http://www.cct.lsu.edu/~eschnett/
Developers mailing list Developers@einsteintoolkit.org http://lists.einsteintoolkit.org/mailman/listinfo/developers
This is the standard Cactus output after running all test cases. Yes, I assume this means that 7 thorns that had runnable test cases (i.e. test cases where all active thorns were compiled in). All Einstein Toolkit thorns were active.
-erik
On Apr 13, 2010, at 19:36 , Allen Gabrielle wrote:
Is the number of tested thorns below actually useful? I assume this is the number of thorns that contained testsuites rather than the number of thorns that were activated in any of the testsuites?
On Apr 13, 2010, at 12:33 AM, Erik Schnetter wrote:
These are results from the (now working again) nightly build tests, in particular on Mac OS X:
Summary for configuration einsteintoolkit
Total available tests -> 80 Unrunnable tests -> 54 Runnable tests -> 26 Total number of thorns -> 105 Number of tested thorns -> 7 Number of tests passed -> 5 Number passed only to set tolerance -> 3 Number failed -> 21
"Unrunnable" means likely that a necessary thorn is not present, such as ADM. "Failed" test, well, fail.
So our success rate is 6%.
-erik
-- Erik Schnetter schnetter@cct.lsu.edu http://www.cct.lsu.edu/~eschnett/
Developers mailing list Developers@einsteintoolkit.org http://lists.einsteintoolkit.org/mailman/listinfo/developers
Yes ... so am thinking we might want to change the script to report in a different way.
On Apr 13, 2010, at 10:39 PM, Erik Schnetter wrote:
This is the standard Cactus output after running all test cases. Yes, I assume this means that 7 thorns that had runnable test cases (i.e. test cases where all active thorns were compiled in). All Einstein Toolkit thorns were active.
-erik
On Apr 13, 2010, at 19:36 , Allen Gabrielle wrote:
Is the number of tested thorns below actually useful? I assume this is the number of thorns that contained testsuites rather than the number of thorns that were activated in any of the testsuites?
On Apr 13, 2010, at 12:33 AM, Erik Schnetter wrote:
These are results from the (now working again) nightly build tests, in particular on Mac OS X:
Summary for configuration einsteintoolkit
Total available tests -> 80 Unrunnable tests -> 54 Runnable tests -> 26 Total number of thorns -> 105 Number of tested thorns -> 7 Number of tests passed -> 5 Number passed only to set tolerance -> 3 Number failed -> 21
"Unrunnable" means likely that a necessary thorn is not present, such as ADM. "Failed" test, well, fail.
So our success rate is 6%.
-erik
-- Erik Schnetter schnetter@cct.lsu.edu http://www.cct.lsu.edu/~eschnett/
Developers mailing list Developers@einsteintoolkit.org http://lists.einsteintoolkit.org/mailman/listinfo/developers
-- Erik Schnetter schnetter@cct.lsu.edu http://www.cct.lsu.edu/~eschnett/
developers@lists.einsteintoolkit.org