| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
that something went wrong. Now it will make sure it does. Also start working on multiple configuration scripts
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
output as it goes
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
warning or error
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
try to run directories with the same name as tests
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
array
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
executable
|
|
|
|
| |
command line), improve reading of configuration file (now it actually rereads configuration file after running update/configure/build...). Remember the model (nightly/experimental) across runs
|
| |
|
|
|
|
| |
CTest
|
| |
|