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
Currently, a workload script can exit with a non-zero error code in two probably scenarios
If the workload itself fails
If the workload run takes more time than an expected duration set as a variable
For new users using the framework, it is not clear what these default values should be or if they work in their cluster. It would take some time and testing to come up with these expected duration values. It would make sense to make it optional for pass/fail criteria to depend on expected duration.
The text was updated successfully, but these errors were encountered:
Agreed that there should be an option to disable the duration comparison functionality with default being false to avoid any confusion like you mentioned. Also the default ( 600 seconds ) is not enough for most of the workloads to complete, so they will fail unless we tweak it to something high. Once we know the gold values, we can enable it in cases like CI to determine pass/fail.
Currently, a workload script can exit with a non-zero error code in two probably scenarios
For new users using the framework, it is not clear what these default values should be or if they work in their cluster. It would take some time and testing to come up with these expected duration values. It would make sense to make it optional for pass/fail criteria to depend on expected duration.
The text was updated successfully, but these errors were encountered: