You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@mkavulich has introduced code to the SRW E2E testing framework that runs and monitors a Rocoto workflow through completion (or various forms of failure) and logs the results.
This functionality would be useful for any app running a Rocoto workflow and could be foundational for building testing frameworks for those apps. It also removes the need for a user to have cron installed, and its use is restricted on some platforms.
The idea is that this code would fit into the uw rocoto tool under a new action named something like monitor (not a requirement) and would take arguments indicating the paths to an XML, a database file, and a log file, and would issue rocotorun and rocotostat alternatively until the workflow fails or completes, logging the status with each iteration.
Mike also added the ability to restart a monitoring session from an existing log file, so we'd likely want to take that into account.
The text was updated successfully, but these errors were encountered:
@mkavulich has introduced code to the SRW E2E testing framework that runs and monitors a Rocoto workflow through completion (or various forms of failure) and logs the results.
This functionality would be useful for any app running a Rocoto workflow and could be foundational for building testing frameworks for those apps. It also removes the need for a user to have cron installed, and its use is restricted on some platforms.
The idea is that this code would fit into the
uw rocoto
tool under a new action named something likemonitor
(not a requirement) and would take arguments indicating the paths to an XML, a database file, and a log file, and would issuerocotorun
androcotostat
alternatively until the workflow fails or completes, logging the status with each iteration.Mike also added the ability to restart a monitoring session from an existing log file, so we'd likely want to take that into account.
The text was updated successfully, but these errors were encountered: