This PR includes changes that upload the testing results to the sdk testing dashboard.
This functionality mainly exists in a new test.py file that is used as a wrapper script to run the tests and capture and upload the results to the testing dashboard. For the SDK, we are curating a limited scope of data in hopes that we can get approval to upload results from computing centers like LLNL. The limited scope includes information like build parameters, results, and the output from running the tests themselves.
Currently the build of the docker containers does not send any results to the dashboard, should we include each build as a test as well? For example, a run in this case would be the entire SDK build, and the tests would be SDK component build.
This PR includes changes that upload the testing results to the sdk testing dashboard.
This functionality mainly exists in a new
test.pyfile that is used as a wrapper script to run the tests and capture and upload the results to the testing dashboard. For the SDK, we are curating a limited scope of data in hopes that we can get approval to upload results from computing centers like LLNL. The limited scope includes information like build parameters, results, and the output from running the tests themselves.Currently the build of the docker containers does not send any results to the dashboard, should we include each build as a test as well? For example, a run in this case would be the entire SDK build, and the tests would be SDK component build.