Description of task
One way of testing graphical simulation scenarios with GitHub actions is with a self-hosted runner. With that we can utilize our own hardware for the actions, and potentially schedule graphical tests in the same way we currently utilize the no-gpu simulations for scheduled tests. This self-runner could aid in the following:
- Schedule daily tests and on pull requests, where all scenarios will be launched one by one, to make sure all of them start correctly.
- Schedule daily tests on a graphical scenario (e.g. aruco detection or more sitaw-auto-control integrated tests) with some kind of randomized initial/final conditions (TODO for vortex-auv no-gpu simulation tests as well) to challenge the solutions.
- Testing of the TACC scenarios, when the software has come so far.
Recommended Reading
Suggested Workflow
Contacts
Description of task
One way of testing graphical simulation scenarios with GitHub actions is with a self-hosted runner. With that we can utilize our own hardware for the actions, and potentially schedule graphical tests in the same way we currently utilize the no-gpu simulations for scheduled tests. This self-runner could aid in the following:
Recommended Reading
Suggested Workflow
Contacts