@@ -22,3 +22,5 @@ Let's put together a list of things we'd like to have in the harness and maybe t
...
@@ -22,3 +22,5 @@ Let's put together a list of things we'd like to have in the harness and maybe t
* Move code that repeats in every test to the inside the harness (e.g. send_to_scheduler, make_batch_script) to make test creation easier
* Move code that repeats in every test to the inside the harness (e.g. send_to_scheduler, make_batch_script) to make test creation easier
* Output test metrics similar to rgt_status.txt, we can have an rgt_metrics.txt to include app specific values (e.g. GTC/checkpoint restart time, S3D/IO rate, etc)
* Output test metrics similar to rgt_status.txt, we can have an rgt_metrics.txt to include app specific values (e.g. GTC/checkpoint restart time, S3D/IO rate, etc)
* We need a machine file that contains machine specific info such as scheduler that we need to make it platform independent. A default file with info for our machines should be part of the repo.