#394: Testsuite log file should contain more information -------------------------+-------------------------------------------------- Reporter: hinder | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: Cactus | Version: Keywords: testsuites | -------------------------+-------------------------------------------------- It is useful to look at the testsuite log file for information about how the tests were run. For example, which compiler was used, and with what compiler options. We need to balance this against providing information which will always change, making diffs hard to read.
The most extreme case would be to output all make variables. Maybe better would be to output CC, CFLAGS, CXX, etc. Another option would be to parse these and say "intel compiler", "gcc", "pgi" etc.
#394: Testsuite log file should contain more information --------------------------+------------------------------------------------- Reporter: hinder | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: Cactus | Version: Resolution: | Keywords: testsuites --------------------------+-------------------------------------------------
Comment (by knarf):
What about including the contents of configs/NAME/config-info?
#394: Testsuite log file should contain more information --------------------------+------------------------------------------------- Reporter: hinder | Owner: Type: enhancement | Status: confirmed Priority: minor | Milestone: Component: Cactus | Version: Resolution: | Keywords: testsuites --------------------------+------------------------------------------------- Changes (by hinder):
* status: new => confirmed
Comment:
This would still be useful to have. The data should be easy to parse in some way, to be displayed on https://einsteintoolkit.org/release- info/parse_testsuite_results.php.
trac@lists.einsteintoolkit.org