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
Weird behavior when cluster's IUT wait timeout is lower than IUT provider's wait timeout: e. g. 3600 vs 43200.
The testrun will be aborted after one hour if no IUT was availiable, however IUT provider will still be waiting for an IUT and possibly check it out later.
Additional Context
No response
Logs
No response
Expected Behavior
The obvious workaround for a typical usage scenario is to make both these timeouts equal. However, IUT provider should not continue waiting/check out IUT if the testrun is no longer requesting it.
Steps To Reproduce
No response
The version of this project/repo, if applicable
No response
The version/edition of the Eiffel Protocol used, if applicable
main
The text was updated successfully, but these errors were encountered:
Description
Weird behavior when cluster's IUT wait timeout is lower than IUT provider's wait timeout: e. g. 3600 vs 43200.
The testrun will be aborted after one hour if no IUT was availiable, however IUT provider will still be waiting for an IUT and possibly check it out later.
Additional Context
No response
Logs
No response
Expected Behavior
The obvious workaround for a typical usage scenario is to make both these timeouts equal. However, IUT provider should not continue waiting/check out IUT if the testrun is no longer requesting it.
Steps To Reproduce
No response
The version of this project/repo, if applicable
No response
The version/edition of the Eiffel Protocol used, if applicable
main
The text was updated successfully, but these errors were encountered: