Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IUT checkout request not aborted after IUT wait timeout expired #329

Open
andmat900 opened this issue Dec 16, 2024 · 0 comments
Open

IUT checkout request not aborted after IUT wait timeout expired #329

andmat900 opened this issue Dec 16, 2024 · 0 comments
Labels
bug Something isn't working Controller

Comments

@andmat900
Copy link
Contributor

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

@andmat900 andmat900 added bug Something isn't working Controller labels Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Controller
Projects
None yet
Development

No branches or pull requests

1 participant